Migrating the form with redirect or iframe form
Would you like to migrate a form with redirect (or iframe form) to an embedded form? This page describes the main parameters and how to use them with the JavaScript client and the REST API.
Redirection | Description |
---|---|
vads_effective_creation_date | Effective date of transaction creation |
vads_identifier | See Charge/CreatePayment.paymentMethodToken |
vads_identifier_status | Status of the SEPA mandate: not supported to this date |
vads_language | Defining the language of the payment form |
vads_page_action | See Charge/CreatePayment.formAction |
vads_payment_certificate | Replaced by a signature mechanism based on HMAC-SHA256 |
vads_url_check_src | Identifying the source of the notification |
vads_result | Operation return code. Corresponds to various fields in the REST API. |
vads_trans_id | The REST API automatically defines the transaction identifier |
vads_trans_date | The REST API automatically defines the transaction date |
vads_effective_creation_date
This parameter is mapped in the transactions[0].creationDate object.
vads_identifier_status
This parameter contains the status of the SEPA mandate. This parameter does not have any equivalent to date, since the REST API only supports card payments.
vads_language
To choose the language of the payment form, you need to define the locale of your choice when loading the JavaScript client with the kr-language parameter.
For example, to display the form in Russian:
You can also define the language at runtime:
KR.setFormConfig({"language": "ru-RU"});
For more information, go to: JavaScript client reference
vads_url_check_src
This parameter has no equivalent in the REST API. The closest approximation to this parameter is transactionDetails.cardDetails.paymentMethodSource.
See reference documentation for more information: Transaction object.
vads_result
This field has several equivalents, depending on the context. For more information, see Transaction lifecycle.
vads_payment_certificate
The signature mechanism is now based on HMAC-SHA256.
Pour plus d'informations sur le fonctionnement de la signature, rendez-vous ici : retour à la boutique ou Utilisation de l'IPN (URL de notification)
vads_trans_date
vads_trans_date has no equivalent. The transaction id is automatically generated by REST web services.
vads_trans_id
vads_trans_id has no equivalent. The transaction id is automatically generated by REST web services. The id is no longer an integer but an alphanumeric UUID of 32 characters.
vads_page_action
We need to use the formAction
parameter of the REST Web Service Charge/CreatePayment :
- PAYMENT: Create a simple transaction. Default behavior.
- REGISTER_PAY: Creation of an alias (token) of the payment method at the same time as the transaction. Does not allow the creation of an alias associated with an IBAN.
- ASK_REGISTER_PAY: Adds a checkbox on the form for creating an alias (token). Does not create an alias associated with an IBAN.
More info: Charge/CreatePayment.
What is the equivalent of vads_identifier?
il faut utiliser la paramètre paymentMethodToken
du Web Service REST Charge/CreatePayment. Notez que l'API REST ne vous permet plus de définir vous-même l'identifiant de l'alias. Il est automatiquement généré par la plateforme sous la forme d'une chaine alphanumérique de 32 caratères de long.
Example of a token: 4b92ad0a0bfe4dd0976a5954f8071b59
What is the equivalent of creating a subscription?
You need to proceed in 2 steps.
- Create a token.
Alternatively, you can use the Web Service Rest Charge/CreatePayment.
- REGISTER_PAY: with parameter
formAction
. - ASK_REGISTER_PAY: with parameter
formAction
.
- REGISTER_PAY: with parameter
Alternatively, you can use the Web Service Rest Charge/CreateToken.
- Create the subscription using the generated alias (link:Charge/CreateSubscription ).