‘Creation of a token when creating a recurring payment with payment’ form

Use case: payment and creation of a recurring payment with token creation.

Under PSD2, strong authentication is required when registering a card. The vads_threeds_mpi field is ignored and the CHALLENGE_MANDATE value is automatically applied.

  1. 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.: mail@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)

    The installment amount cannot be set to 0.

    n..12 E.g.: 3000 for 30,00 EUR
    vads_sub_currency 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.

    If you request the creation of a recurring payment to debit the payment method holder daily (RRULE:FREQ=DAILY;INTERVAL=1), and the requested effective date (vads_sub_effect_date) corresponds to the recurring payment creation date, then when the payment gateway processes this recurring payment the following morning (between midnight and 5a.m.), 2 payments will be created:
    • The payment from the previous day (that corresponds to the effective date)
    • And the payment from the current day

    To avoid this, it is recommended to transmit an effective date the day after the recurring payment is created.

    string

    The recurring payments can be made daily, weekly or monthly.

    It is possible to specify the number of the day or the month (e.g. “the 10th of the month”, “every 3 months”).

    Note: the string must not contain space characters.

    Examples:
    • In order to define a weekly recurring payment:
      RRULE:FREQ=WEEKLY
    • In order to define a recurring payment every two weeks, on the same day and every 7 days:
      RRULE:FREQ=WEEKLY;INTERVAL=2
    • To schedule installment payments on the last day of each month for 12 months:
      RRULE:FREQ=MONTHLY;
      BYMONTHDAY=28,29,30,31;
      BYSETPOS=-1;COUNT=12
    • To schedule installment payments on the 10th of each month for 12 months:
      RRULE:FREQ=MONTHLY;
      COUNT=12;BYMONTHDAY=10
    vads_sub_effect_date Recurring payment start date. n8 E.g.: 20210601
    vads_trans_date Date and time of the payment form in UTC format. n14 E.g.: 20190501130025
    vads_trans_id Unique ID of a transaction. n6 E.g.: 123456
    vads_version Version of the exchange protocol. string V2
    Note:
    The vads_sub_effect_date time value must not be in the past.

  2. 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.

    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.

  3. Add optional fields according to your requirements (see chapter Using additional features).
  4. Compute the value of the signature field using all the fields of your form starting with vads_ (see chapter Computing the signature).

The list of fields returned in the notification is described in the chapter Creating a token during creation of a recurring payment with payment.