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:

  <script 
   src="<?php echo $client->getClientEndpoint();?>/static/js/krypton-client/V4.0/stable/kr-payment-form.min.js"
   kr-public-key="<?php echo $client->getPublicKey();?>"
   kr-language="ru-RU"
   kr-post-url-success="paid.php">
  </script>

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.

For more information on the signature, go to: Browser return or Using the IPN (notification URL)

vads_trans_date

vads_trans_date n’a pas d’équivalent. L’id de transaction est généré automatiquement par les web services REST

vads_trans_id

vads_trans_id n’a pas d’équivalent. L’id de transaction est généré automatiquement par les web services REST. L’identifiant n’est plus un nombre entier (integer) mais un UUID alphanumérique de 32 caractères.

vads_page_action

You must use the formAction parameter of the Charge/CreatePayment RESTful Web Service. To this date, only two options are available:

  • PAYMENT
  • REGISTER_PAY

You can simulate the REGISTER option by creating a 1-euro transaction in manual validation mode. For more information, go to: 1-click payment.

The ASK_REGISTER_PAY and REGISTER_UPDATE options are scheduled for the beginning of 2019.

What is the equivalent of vads_identifier?

You must use the paymentMethodToken parameter of the Charge/CreatePayment RESTful Web Service. Note that the REST API does not allow you to define the token identifier yourself. It is automatically generated by the gateway in the form of a 32-character alphanumeric string.

Example of a token: 4b92ad0a0bfe4dd0976a5954f8071b59