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.

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 how the signature works, go here: return to the store or Using the IPN (notification URL)

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?

You must use the paymentMethodToken parameter of the Charge/CreatePayment REST Web Service. Note that the REST API no longer allows you to define the alias identifier yourself. It is automatically generated by the platform as a 32-character alphanumeric string.

Example of a token: 4b92ad0a0bfe4dd0976a5954f8071b59

What is the equivalent of creating a subscription?

You need to proceed in 2 steps.

1. Create a token.

• Alternatively, you can use the Web Service Rest Charge/CreatePayment.

  • REGISTER_PAY: with parameterformAction.
  • ASK_REGISTER_PAY: with parameterformAction.

• Alternatively, you can use the Web Service Rest Charge/CreateToken.

2. Create the subscription using the generated alias (link:Charge/CreateSubscription ).