Creating a 'Creation of a token during creation of a recurring payment with payment' form
Use case: payment and creation of a recurring payment with token creation.
- Use all the fields presented in the table below to create your form.
Field name Description Format Value vads_page_action Action to perform enum REGISTER_PAY_SUBSCRIBE vads_amount Payment amount (in the smallest currency unit) n..12 E.g.: 3000 for 30,00 EUR vads_ctx_mode Operating mode. enum TEST or PRODUCTION vads_currency Code of the currency used for the payment. n3 E.g.: 978 for euro (EUR) vads_cust_email Buyer’s e-mail address. ans..150 E.g.: email@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_sub_amount Installment amount (in the smallest currency unit) n..12 E.g.: 3000 for 30,00 EUR vads_sub_
Code of the currency used for the recurring payment. n3 E.g.: 978 for euro (EUR) vads_sub_desc Rule for recurring payments to apply according to the iCalendar RFC5545 specification. string E.g.: RRULE:FREQ=MONTHLY;COUNT=12; BYMONTHDAY=10 (for installment payments occurring on the 10th day of each month for 12 months) vads_sub_
Recurring payment start date. n8 E.g.: 20150601 vads_trans_
Date and time of the payment form in UTC format. n14 E.g.: 20150501130025 vads_trans_id Unique transaction ID. n6 E.g.: 123456 vads_version Version of the exchange protocol. string V2Note:The vads_sub_effect_date time value must not have passed
- Use the vads_identifier field if you wish to generate the identifier of the token associated with the payment method.The token format must not be an..32. This format is reserved for tokens generated by the payment gateway.
- Add optional fields according to your requirements (see chapter Using additional features).
- Compute the value of the signature field using all the fields of your form starting with vads_ (see chapter Computing the signature).