Creating a payment form for split payments

Characteristics of a split payment (several payment methods):

  • All the transactions of a split payment are combined within a payment sequence.
  • All the transactions of a payment sequence have the same transaction identifier, but a different sequence number.
  • The number of the first transaction of the sequence is 1, the number of the second one is 2, etc.


The purchase was partly paid with a Titre-Restaurant and the remaining amount was paid with a bank card.

To generate the payment form:

  1. Use all the fields presented in the table below to create your payment form.
    Table 1. List of fields - Split payment (several payment methods)
    Field name Description Format Value
    vads_page_action Action to perform enum PAYMENT
    vads_ctx_mode Defines the mode of interaction with the payment gateway. enum TEST or PRODUCTION
    vads_action_mode Card data acquisition mode enum INTERACTIVE
    vads_site_id Shop ID n8 E.g.: 12345678
    vads_trans_date Date and time of the payment form in UTC format n14 E.g.: 20170701130025
    vads_version Version of the exchange protocol with the payment gateway enum V2
    vads_amount Payment amount in the smallest currency unit (cents for euro). n..12 E.g.: 3000 for 30,00 EUR
    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_acquirer_transient_data Amount payable by Titre-Restaurant (in the smallest currency unit) json Example for an eligible amount of EUR 17.25:

    vads_acquirer_transient_data ={"CONECS":{"eligibleAmount":"1725"}}

    vads_payment_config Payment type enum SINGLE
    vads_trans_id Transaction number n6 E.g.: 123456
    vads_capture_delay Capture delay n..3 0
    vads_validation_mode Validation mode n1 0 (Automatic)

    Signature guaranteeing the integrity of the requests exchanged between the merchant website and the payment gateway.


    See Computing the signature

  2. Set the vads_capture_delay field to 0.
    Note: deferred capture is not taken into account in case of a payment by Titre-Restaurant. A value different from 0 will be ignored.
  3. Set the vads_validation_mode field to 0.
    Note: manual validation is not taken into account in case of a meal voucher payment. A value different from 0 will be ignored.
  4. Populate the vads_acquirer_transient_data field to submit the eligible amount in Titre-Restaurant.
    Example for an eligible amount of €17.25: {"CONECS":{"eligibleAmount":"1725"}}
  5. Add optional fields depending on your requirements (see chapter Using additional features of the Hosted Payment PageImplementation guide available on our website).