Lifecycle of a recurring payment

The recurring payment starts on its effective date.

The payment gateway starts creating payments following the schedule determined by the recurring payment rule sent in the form of recurring payment creation (vads_sub_desc field).

Upon each installment, if the Instant Payment Notification URL when creating a recurring payment rule is enabled and correctly configured, the merchant website will receive the payment result via their notification URL (IPN).

In case of failure:

  • the merchant will not be notified by e-mail,
  • the payment will not be automatically presented once again.

If the payment method has reached its expiry date, a refused transaction is created without a call to the issuing bank. The error details (vads_payment_error) are set to 8 - The card expiration date does not allow this action.

If the payment method data has been purged following 15 moths of inactivity, a refused transaction is created without a call to the issuing bank. The error details (vads_payment_error) are set to 107 - The payment method associated with the token is no longer valid.