error 69 - Error 69 - vads_sub_effect_date

In PRODUCTION mode, if your buyer gets an error message such as:

An error occurred during the payment request, please make sure that the posted parameters match the ones specified in the documentation.

It becomes impossible to make the payment and the transaction is definitively lost.

You will receive an e-mail notification containing the form that the gateway was unable to process and the value of the invalid field.

We invite you to check the following reason(s) to resolve the issue:

The effective date is not submitted in the YYYYMMDD format (year, month, day).
vads_sub_effect_date is a mandatory parameter used for creating a recurring payment. It allows to define an effective date for a recurring payment. The effective date indicates when the recurring payment starts. The format of this date is YYYYMMDD. Example: For October 17, 2019, the value of the vads_sub_effect_date field must be 20191017.

The effective date is not submitted in the YYYYMMDD format (year, month, day).

vads_sub_effect_date is a mandatory parameter used for creating a recurring payment. It allows to define an effective date for a recurring payment.

The effective date indicates when the recurring payment starts. The format of this date is YYYYMMDD.

Example:

For October 17, 2019, the value of the vads_sub_effect_date field must be 20191017.

The effective date has passed.
The effective date that determines when to start the recurring payment cannot be in the past. Verify that the vads_sub_effect_date value is consistent with the date of creation of the recurring payment. Example: If the date of recurrent payment creation is October 17, 2019, the vads_sub_effect_date field cannot be populated with October 15, 2019.

The effective date has passed.

The effective date that determines when to start the recurring payment cannot be in the past. Verify that the vads_sub_effect_date value is consistent with the date of creation of the recurring payment.

Example:

If the date of recurrent payment creation is October 17, 2019, the vads_sub_effect_date field cannot be populated with October 15, 2019.

The effective date does not respect the pre-notification delay defined for SEPA DD payments.
In case of a SEPA Direct Debit recurring payment, a pre-notification must be sent at least 14 calendar days before the effective date of the direct debit. Upon a bilateral agreement, this period may be reduced but cannot be less than the date of creation of the recurring payment. Verify that the value of vads_sub_effect_date corresponds to the defined pre-notification date.

The effective date does not respect the pre-notification delay defined for SEPA DD payments.

In case of a SEPA Direct Debit recurring payment, a pre-notification must be sent at least 14 calendar days before the effective date of the direct debit. Upon a bilateral agreement, this period may be reduced but cannot be less than the date of creation of the recurring payment.

Verify that the value of vads_sub_effect_date corresponds to the defined pre-notification date.

Categories

Tags

error 69 - Error 69 - vads_sub_effect_date