|vads_effective_creation_date||Effective date of transaction creation|
|vads_identifier_status||Status of the SEPA mandate: not supported to this date|
|vads_language||Defining the language of the payment form|
|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|
This parameter is mapped in the transactions.creationDate object.
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.
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:
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.
This field has several equivalents, depending on the context. For more information, see Transaction lifecycle.
The signature mechanism is now based on HMAC-SHA256.
vads_trans_date has no equivalent. The transaction id is automatically generated by REST web services.
vads_trans_id has no equivalent. The transaction ID is automatically generated by REST web services. The identifier is no longer an integer but an alphanumeric 32 character UUID.
You must use the formAction parameter of the Charge/CreatePayment RESTful Web Service. To this date, only two options are available:
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.
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