Debt Recovery Workflows {#um-models-flows-common-debt-recovery} =============================================================== Debt recovery workflows show how to use debt recovery transactions to collect outstanding debt when an aggregated end-of-day transaction is declined. Card schemes require merchants to support merchant-initiated debt recovery. This type of transaction can also be required to remove a card from a deny list. Each card scheme has its own transaction-processing rules for debt recovery retry attempts, transaction time limits, and related mass transit transactions. For more information, see each card scheme's rules for transit debt recovery retry attempts and transaction time limits. IMPORTANT Use a debt recovery transaction to remove a card from a deny list. This action must be completed within one hour of receiving the authorization approval. These debt recovery transactions are supported: * A merchant-initiated transaction that uses the card number. * A tap-initiated transaction that uses the EMV track 2 equivalent and EMV tags created when the cardholder re-enters the transit system. * A cardholder-initiated transaction that the customer requests by contacting you. {#um-models-flows-common-debt-recovery_ul_kxv_bsd_xhc} When a debt recovery transaction is declined, you can request payment using the First Ride Risk liability model. For more information, see each card scheme's rules for mass transit transaction chargebacks. Merchant-Initiated Debt Recovery -------------------------------- A *merchant-initiated* (MIT) *debt recovery* transaction is a deferred authorization that originates from your back office. This type of transaction is also called *auto-debt recovery*. The authorization resubmission typically uses the card number and references the original, end-of-day transaction that was declined. Visa allows up to six authorization resubmissions within 14 days. #### Figure: {#um-models-flows-common-debt-recovery_fig_glc_2d2_j3c} Visa Merchant-Initiated Debt Recovery Workflow ![Diagram showing Visa's Merchant-Initiated Debt Recovery workflow](/content/dam/documentation/cybs/en-us/topics/payments-processing/card-processing/mass-transit/images/merchant-init-debt-recovery-flow-475x345.svg/jcr:content/renditions/original) 1. When the number of retry attempts for the MIT debt recovery transaction exceeds the card scheme's limit, stop further processing and keep the card on the deny list. 2. When the amount is below the debt recovery amount limit, send a sale request. See [Merchant-Initiated Sale for Visa Debt Recovery with Stored Card Data](/docs/cybs/en-us/urban-mobility/developer/ctv/rest/mass-transit/um-processing-emv-vpc/um-processing-sale-mit-intro.md ""). 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. Scheduled Debt Recovery Transaction Resubmission ------------------------------------------------ A *scheduled debt recovery* transaction is a system-generated transaction that originates from your back office. This transaction typically uses the card number and references the original, end-of-day transaction that was declined. Multiple authorization resubmissions might be triggered within 14 days. #### Figure: {#um-models-flows-common-debt-recovery_fig_ibv_nh1_zhc} Scheduled Debt Recovery Workflow ![Workflow diagram showing Scheduled Debt Recovery workflow](/content/dam/documentation/cybs/en-us/topics/payments-processing/card-processing/mass-transit/images/system-gen-debt-recovery-flow-600x345.svg/jcr:content/renditions/original) 1. You configure your payment system to generate scheduled debt recovery authorization requests. 2. The scheduled authorizations attempt debt recovery submissions within 14 days of the initial transaction. 3. When the number of retry attempts for the scheduled debt transaction exceeds the card scheme's limit, stop further processing and keep the card 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 --------------------------- A *tap-initiated debt recovery* transaction 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 transaction is attempted in real time while the cardholder is at the gate. The authorization request includes the EMV track 2 equivalent and EMV tags from the new tap, and a future capture date. #### Figure: {#um-models-flows-common-debt-recovery_fig_xpp_lr3_k3c} Tap-Initiated Debt Recovery Workflow ![Diagram showing Tap-Initiated Debt Recovery Workflow](/content/dam/documentation/cybs/en-us/topics/payments-processing/card-processing/mass-transit/images/tap-initiated-debt-recovery-flow-260x425.svg/jcr:content/renditions/original) 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 ---------------------------------- A *cardholder-initiated debt recovery* transaction occurs when the cardholder contacts you. The method of contact depends on where the transaction occurred such as on your e-commerce website or by phone or email for a mail order or telephone order (MOTO) transaction. For information about e-commerce or MOTO payment services, see the [*Payments Developer Guide*](https://developer.cybersource.com/docs/cybs/en-us/payments/developer/ctv/rest/payments/payments-intro.md ""). #### Figure: {#um-models-flows-common-debt-recovery_fig_ltd_wr3_k3c} Cardholder-Initiated Debt Recovery Flow ![Diagram showing Cardholder-Initiated Debt Recovery Flow](/content/dam/documentation/cybs/en-us/topics/payments-processing/card-processing/mass-transit/images/cardholder-init-debt-recov-flow-240x410.svg/jcr:content/renditions/original) 1. The cardholder contacts you through your website or by phone or email for a MOTO transaction. 2. You process a card-not-present (CNP) 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.