• France
status page
demonstrations
assistance
FAQContact support
Search
Categories
Tags
English
French
English
Homepage
Use cases
Create a payment
Create an installment payment
Create a multi-card (split) 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

Analyzing the result of an installment payment

  1. You have requested the creation of a recurring payment with fixed amounts and due dates. You will receive a notification for each due date, identified by the value of the vads_url_check_src field:
    Value Description
    REC

    Value is sent only for recurring payments if the merchant has configured the Instant Payment Notification "URL when creating recurring payments rule"

    Not applicable for one-off direct debit on SEPA.
  2. Identify the mandate and the recurring payment that correspond to the installment by testing the following fields:
    Field Description
    vads_identifier Mandate reference (UMR)
    vads_subscription Recurring payment ID
    vads_sequence_number Sequence number of the recurring payment
  3. Retrieve the transaction details:
    Field name Description
    vads_acquirer_network Acquirer network code. Populated with SEPA.
    vads_amount Payment amount (in cents).
    vads_currency Numeric code of the EUR currency, valued at 978.
    vads_occurrence_type Type of sequence.

    Populated with RECURRENT_INTERMEDIAIRE.

    vads_presentation_date Returns the requested due date.
    vads_trans_id Transaction identifier transmitted by the Merchant.
    vads_trans_status Transaction status (see table below).
    vads_trans_uuid Transaction identifier generated by the gateway.

    The transaction status is returned in the vads_trans_status field:
    Value Description
    AUTHORISED

    Accepted, waiting for capture

    A pre-notification has been sent. The direct debit is waiting to be presented at the bank.

    REFUSED

    Refused

    Status sent in case of 1-click payment when some rules have been enabled in the Risk assessment tab or when the mandate is expired.

    AUTHORISED_TO_VALIDATE

    To be validated

    The direct debit request has been made in “manual validation” mode. The merchant must manually validate the transaction in the Merchant Back Office to authorize the transfer of the mandate to the bank.

    The pre-notification will only be sent after the transaction has been validated.

    An automatic e-mail is processed every day, several times per day (every 3 hours) that does not require any intervention on your behalf.

    The transaction can be validated as long as the expiration date of the authorization request has not passed. If the authorization validity period has been passed, the payment takes Expired status. This status is final.

    WAITING_AUTHORISATION

    Waiting for authorization

    WAITING_AUTHORISATION_TO_VALIDATE

    To be validated and authorized

    The capture delay in the bank exceeds the authorization validity period.

    The Merchant must manually validate the transaction for the authorization request and the capture to occur.

© 2025 {'|'} All rights reserved to Scellius
25.18-1.11