• France
Merchant Back Office
assistance
FAQContact support
Search
Categories
Tags
English
French
English
Homepage
Use cases
Create a payment
Create an installment payment
Create a payment by Alias (Token)
Create a payment link
Create a recurring payment
Manage subscriptions
Manage your transactions (refund, cancel...)
Analyze your reports
API docs
Embedded Form
REST API
Hosted payment
Mobile payment
File exchange
Snippets
Payment methods
Plugins
Guides
Merchant Back Office
Functional guides

Creating a deferred payment

A payment is considered a deferred payment if:

  • the amount is debited once,
  • the capture delay is strictly more than 0 days.

    The capture date cannot be more than 12 months after the payment request registration date.

There are two types of deferred payments:

  • Capture delay less than 7 days

    An authorization request for the total amount is sent. If the merchant has not made any modifications, the payment is captured by the bank on the requested capture day.

  • Capture delay more than 7 days

    An authorization request for 100 XPF is made to check the validity of the card.

    If this authorization for XPF 100 is accepted, the payment request is registered.

    An authorization request for the total amount is made one day before the requested capture.

    The result is notified to the merchant website due to the Instant Payment Notification URL on batch authorization rule.

    The payment might be accepted or refused. Therefore, the merchant must be extremely attentive with this payment type and make sure to deliver the items/services to the buyer.

  1. Use all the fields presented in the table below to create your payment form.
    Field name Description Format Value
    vads_payment_cards Allows to force the card type to be used.

    It is recommended to provide a different payment button for each payment method on the merchant website.

    enum
    • PRV_BDP to call the HOA PRIVATIVE card payment button.
    • PRV_BDT to call the Tiare card payment button.
    • PRV_OPT to call the MARARA payment button.
    • PRV_SOC to call the Banque SOCREDO payment button.
    • PRV_SMART_CARD to call the BRED Smart Card payment button.
    vads_site_id Shop ID n8 E.g.: 12345678
    vads_ctx_mode Mode of interaction with the payment gateway enum TESTorPRODUCTION
    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_trans_date Date and time of the payment form in UTC format n14

    Respect the YYYYMMDDHHMMSS format

    E.g.: 20200101130025
    vads_amount Payment amount in the smallest currency unit n..12 E.g.: 4525 for 4525 XPF
    vads_currency Numeric currency code to be used for the payment, in compliance with the ISO 4217 standard (numeric code). n3 E.g.: 953 for CFP Franc (XPF)
    vads_action_mode Acquisition mode for payment method data enum INTERACTIVE
    vads_page_action Action to perform enum PAYMENT
    vads_version Version of the exchange protocol with the payment gateway enum V2
    vads_payment_config Payment type enum SINGLE
    vads_capture_delay Delay before capture in the bank, the value must be greater than 0 n..3 E.g.: 3
    vads_validation_mode Specifies the validation mode of the transaction (manually by the merchant, or automatically by the payment gateway). n1 0or 1 or absent or empty
  2. Add optional fields according to your requirements (see chapter Using additional features.
  3. Compute the value of the fieldsignatureusing all the fields of your form that start withvads_(see chapter Computing the signature).
© 2025 {'|'} All rights reserved to PayZen by OSB
25.22-1.11