Batch Gateway Reconciliation event mapping between Zuora and GoCardless

This task outlines the event mapping process between Zuora and GoCardless during the gateway reconciliation batch job, which includes parsing records into events and matching them with corresponding transactions.

The gateway reconciliation batch job on the GoCardless side starts at 6:30 am PT every day. Within a GR job, every record in the gateway reconciliation report is parsed into an event and matched with the corresponding Zuora transaction.

The following table lists the event mapping between GoCardless and Zuora in gateway reconciliation.


Object	GoCardless Action	Zuora Event	Zuora Action
Mandate	reinstated	MandateReinstated	Zuora reactivates the payment method.
Mandate	canceled	MandateCanceled	Zuora closes the payment method.
Mandate	failed	MandateRejected	Zuora closes the payment method.
Mandate	expired	MandateExpired	Zuora closes the payment method.
Mandate	resubmission_requested	MandateReinstated	Zuora reactivates the payment method.
Payment	customer_approval_denied	TransactionRejected	Zuora updates the Gateway State to "Failed to Settle" on the Payment transaction. Zuora creates an external refund with the reason code set to "Payment Rejection" if the code is active in the Reason Codes list. Otherwise, Zuora creates an external refund with the reason code set to the default reason code in the list.
Payment	confirmed	TransactionSettled	Zuora updates the Gateway State to "Settled" and the Settled On date field of the Payment event.
Payment	cancelled	TransactionRejected	Zuora updates the Gateway State to "Failed to Settle" on the Payment transaction. Zuora creates an external refund with the reason code set to "Payment Rejection" if the code is active in the Reason Codes list. Otherwise, Zuora creates an external refund with the reason code set to the default reason code in the list.
Payment	failed	TransactionRejected	Zuora updates the Gateway State to "Failed to Settle" on the Payment transaction. Zuora creates an external refund with the reason code set to "Payment Rejection" if the code is active in the Reason Codes list. Otherwise, Zuora creates an external refund with the reason code set to the default reason code in the list.
Payment	charged_back	TransactionReversed	Optionally, Zuora creates an external refund with the reason code set to "Payment Reversal" if the code is active in the Reason Codes list. Otherwise, Zuora creates an external refund with the reason code set to the default reason code in the list.
Payment	late_failure_settled	TransactionReversed	Optionally, Zuora creates an external refund with the reason code set to "Payment Reversal" if the code is active in the Reason Codes list. Otherwise, Zuora creates an external refund with the reason code set to the default reason code in the list.
Refund	paid	TransactionSettled	Zuora updates the Gateway State to "Settled" and the Settled On date field of the Refund event.
Refund	refund_settled	TransactionSettled	Zuora updates the Gateway State to "Settled" and the Settled On date field of the Refund event.

For GoCardless BACS Direct Debit transactions, Zuora processes valid charged_back events received through Gateway Reconciliation even when the events are received after the generic dispute window used for other payment schemes. Zuora updates the associated Payment to reflect the chargeback, reopens the related invoice, and restores the invoice's outstanding balance.

Duplicate BACS chargeback events are processed idempotently and do not cause repeated Payment or Invoice state changes. The reopened invoice can re-enter the applicable dunning or retry flow according to the tenant's configuration.

This behavior applies only to GoCardless BACS Direct Debit transactions. Processing for other payment schemes and gateways is unchanged.

Welcome to Zuora Product Documentation

Explore our rich library of product information

Batch Gateway Reconciliation event mapping between Zuora and GoCardless

zuora-footer