Debt Recovery Workflows

A debt recovery transaction is required so that you can retrieve outstanding debt if the end-of-day transaction is declined. A debt recovery transaction is also required in order to remove a card from a deny list. You must remove the card from the deny list within one hour of receiving the authorization approval. These are the ways to recover debt:
  • Scheduled transaction, resubmitted using the card number.
  • Tap-initiated transaction using the EMV track 2 equivalent and EMV tags created when the cardholder returns to enter the transit system.
  • Cardholder-initiated transaction through an e-commerce website.
When the debt recovery transaction is declined, you can request payment using the first ride risk liability model. See the card scheme rules for mass transit transaction chargebacks.

Scheduled Debt Recovery

A scheduled debt recovery is a system-generated transaction that originates from your back office. This transaction typically references the original declined end-of-day transaction and uses the card number. Multiple authorization resubmissions might be triggered within 14 days.

Figure:

Scheduled Debt Recovery Flow
Flow diagram illustrating the merchant-initiated Visa debt recovery process.
  1. You set up a scheduled debt recovery authorization request process within your operating system.
  2. The scheduled authorization(s) attempt debt recovery submissions within 14 days of the initial transaction.
  3. When the amount exceeds the debt recovery amount limit, the card remains on the deny list.
  4. When the amount is below the debt recovery amount limit, send a sale request.
  5. When the transaction is declined, keep the card on the deny list.
  6. When the transaction is successful, remove the card from the deny list.

Tap-Initiated Debt Recovery

Tap-initiated debt recovery occurs when the cardholder returns to the transit gate, and the validator recognizes a new contactless tap.
You can deny the rider entrance unless the tap-initiated debt recovery is attempted in real time while the cardholder is at the gate. The authorization request uses the EMV track 2 equivalent and EMV tags from the new tap and includes a future capture date.

Figure:

Tap-Initiated Debt Recovery Flow
Flow diagram illustrating the tap-initiated debt recovery process.
  1. The cardholder taps their card to enter the transit system.
  2. You submit a new authorization request using the EMV track 2 equivalent and EMV tags created by the validator and a capture date in the future.
  3. When the transaction is declined, keep the card on the deny list.
  4. When the transaction is successful, remove the card from the deny list.

Cardholder-Initiated Debt Recovery

Cardholder-initiated debt recovery occurs when the cardholder contacts you for debt recovery.
For e-commerce payment services, see the
Payments Developer Guide
 .

Figure:

Cardholder-Initiated Debt Recovery Flow
Flow diagram illustrating the tap-initiated debt recovery process.
  1. Cardholder contacts you through your website or by phone call.
  2. You process a card-not-present authorization.
  3. When the request is successful, remove the card from the deny list.
  4. When the request fails, leave the card on the deny list.