Lifecycle of a recurring payment with anticipated authorization

Thanks to this option, a payment that was rejected for a non fraud-related reason (see chapter Return codes of the authorization request) can be presented again automatically until the scheduled capture date at the bank.

As soon as the option is enabled for the shop, recurring payments are created 6 days before the date anticipated by the recurring payment rule.

It is necessary to enable the Instant Payment Notification URL on batch authorization rule via your Expert Back Office (see chapter Setting up a notification on batch authorization).

D-6: Creating a recurring payment

  • The authorization request is accepted
    • The payment will remain waiting for capture until the initially scheduled date.
    • A call to the notification URL will be triggered if the Instant Payment Notification URL when creating a recurring payment rule is enabled. The request will contain the following values:
      Field name Value
      vads_url_check_src REC
      vads_trans_status AUTHORISED

  • The authorization request is rejected for a fraud-related reason
    • The payment is definitively rejected.
    • A call to the notification URL will be triggered if the Instant Payment Notification URL when creating a recurring payment rule is enabled. The request will contain the following values:
      Field name Value
      vads_url_check_src REC
      vads_trans_status REFUSED

  • The authorization request is rejected for a non fraud-related reason
    • The payment will remain waiting for authorization.
    • A call to the notification URL will be triggered if the Instant Payment Notification URL on batch authorization rule is enabled. The request will contain the following values:
      Field name Value
      vads_url_check_src REC
      vads_trans_status WAITING_AUTHORISATION

D-5, D-4, D-3: Payment re-presentation

  • The authorization request is accepted
    • The payment will remain waiting for capture until the initially scheduled date.
    • A call to the notification URL will be triggered if the Instant Payment Notification URL on batch authorization rule is enabled. In this case, the request will contain the following values:
      Field name Value
      vads_url_check_src BATCH_AUTO
      vads_trans_status AUTHORISED

  • The authorization request is rejected for a fraud-related reason
    • The payment is definitively rejected.
    • A call to the notification URL will be triggered if the Instant Payment Notification URL on batch authorization rule is enabled. In this case, the request will contain the following values:
      Field name Value
      vads_url_check_src BATCH_AUTO
      vads_trans_status REFUSED

  • The authorization request is rejected for a non fraud-related reason
    • The payment will remain waiting for capture until the scheduled date.
    • A call to the notification URL will be triggered if the Instant Payment Notification URL on batch authorization rule is enabled. In this case, the request will contain the following values:
      Field name Value
      vads_url_check_src BATCH_AUTO
      vads_trans_status WAITING_AUTHORISATION

D-2: Last payment re-presentation

  • The authorization request is accepted
    • The payment will remain waiting for capture until the initially scheduled date.
    • A call to the notification URL will be triggered if the Instant Payment Notification URL on batch authorization rule is enabled. In this case, the request will contain the following values:
      Field name Value
      vads_url_check_src BATCH_AUTO
      vads_trans_status AUTHORISED
  • The authorization request is rejected (regardless of the reason)
    • The payment is definitively rejected.
    • A call to the notification URL will be triggered if the Instant Payment Notification URL on batch authorization rule is enabled. In this case, the request will contain the following values:
      Field name Value
      vads_url_check_src BATCH_AUTO
      vads_trans_status REFUSED

D: Capture of the transaction

The payment is automatically captured.

No calls to the Notification URL will be triggered.

Notes

  • Payment rejection between D-6 and D-2

    When the payment is definitively rejected, you must make sure that the access to the service for which the recurring payment was created is canceled on the scheduled date and not on the day when the payment rejection was received.

  • Termination of a recurring payment

    When the buyer cancels their recurring payment, the merchant must cancel the already scheduled payments.