Use case: offer the possibility to create a token during a payment.
| Field name | Description | Format | Value |
|---|---|---|---|
| vads_page_action | Action to perform | enum | ASK_REGISTER_PAY |
| vads_amount | Payment amount in the smallest currency unit (cents for euro) | n..12 | E.g.: 4525 for EUR 45.25 |
| vads_ctx_mode | Mode of interaction with the payment gateway | enum | TEST orPRODUCTION |
| vads_currency | Numeric currency code to be used for the payment, in compliance with the ISO 4217 standard (numeric code). | n3 | E.g.: 978 for euro (EUR) |
| vads_cust_email | Buyer’s e-mail address | ans..150 | E.g.: abc@example.com |
| vads_action_mode | Acquisition mode for payment method data | enum | INTERACTIVE |
| vads_payment_config | Payment type | enum | SINGLE |
| vads_site_id | Shop ID | n8 | E.g.: 12345678 |
| vads_trans_date | Date and time of the payment form in UTC format | n14 | Respect the YYYYMMDDHHMMSS format E.g.: 20200101130025 |
| vads_trans_id | Transaction number. Must be unique within the same day (from 00:00:00 UTC to 23:59:59 UTC). Warning: this field is not case sensitive. | an6 | E.g.: xrT15p |
| vads_version | Version of the exchange protocol with the payment gateway | enum | V2 |
| signature | Signature guaranteeing the integrity of the requests exchanged between the merchant website and the payment gateway. | ans..44 | Compute the value of the signature field using all the fields of your form starting with vads_ (see chapter Computing the signature). |
If you have activated the detection of token uniqueness, the value of the vads_identifier field transmitted in the form can be different from the one present in the notification if the payment method is already associated with another token.
The list of fields returned in the notification is described in the chapter Payment with the token creation option for the cardholder.
