Overview

This article explains how card-based debt repayment transactions work on the Authorize.net platform. It covers how customers repay a balance, loan, or other owed amount using a credit or debit card through the Authorize.net Application Programming Interface (API).

Card network and issuer validations, along with processor routing, determine authorization, capture, and settlement behavior for these transactions. This article is intended to help you understand what to expect, how to configure your integration correctly, and how to handle common issues.

This article applies to: Merchants using Authorize.net for card-based debt repayment flows via the API, specifically on TSYS or First Data Nashville (FDC) processor connections.

This article does not apply to: Non-card repayment methods (e.g., ACH, bank transfers), general purchase transactions, or processors not listed in this article unless confirmed by Authorize.net Support.

Benefits and Impacts

Card-based debt repayment on Authorize.net provides the following benefits and considerations:

• Provides a straightforward way for customers to repay balances using credit or debit cards.
• Card issuer and processor validation enables real-time approvals or declines. Declines may occur for reasons similar to standard purchase authorizations, including card status, account limits, and issuer policies.

Note: Processor and issuer behavior can vary by acquirer and card brand. Confirm expected behavior with your acquirer before sending production traffic.

What You Should Know and Do

• Accept and document which card types and tokenized or digital wallet flows you will support for repayments.
• Expect standard card authorization checks. Handle declines with clear customer communications and alternate payment options.
• If you use tokenization or digital wallets such as Apple Pay or Google Pay, confirm how tokens are routed and whether any additional token or cryptogram fields are required by your processor.
• If you use a third-party vault, connector, or processor, confirm routing and handling for repayment transactions with that provider.
• Retain payer authorization records and repayment agreements to assist with reconciliation and dispute resolution.

Processor Support and Enablement

Support for card-based debt repayment depends on your processor implementation and Authorize.net enablement. The table below summarizes current processor support.

Processor support may vary by card brand and transaction type. If your processor is not listed above, contact Authorize.net Support for guidance.

Implementation Notes

Authorize.net API Behavior

• Supported method: Card debt repayment is supported via the Authorize.net API only. Virtual Terminal (VT) support is not yet available and is expected in Q3.
• How to submit: Use the createTransactionRequest API call and include the debtRepaymentIndicator boolean field.
• Recommended setting: Set debtRepaymentIndicator = true for repayment flows, including:
  • Credit card bill pay
  • Loan repayments
  • Certain installment payments
• Note: Processor or network rules may require this flag for correct routing or reporting. Consult your acquirer or Authorize.net Support for processor-specific requirements.
• Processor availability: Currently available for TSYS and FDC processor connections only. Confirm with Authorize.net Support or your acquirer for the latest updates.
• Testing: Verify behavior in your sandbox or test environment to observe authorization and routing outcomes before going to production.

Best Practices

• Confirm supported card brands and token or digital wallet flows with your acquirer or processor before sending production traffic.
• Test repayment flows in sandbox or test environments and document decline behaviors and edge cases.
• Ensure payer authorization and documentation are retained for dispute handling and reconciliation.
• Document alternative repayment paths for declined transactions — such as alternate card, manual reconciliation, or store credit — and prepare customer communication templates.
• If you use tokenization or digital wallets, log token and cryptogram fields securely to aid troubleshooting with your token provider or processor.

Troubleshooting and Common Scenarios

Real-Time Decline on Repayment

The issuer declined the credit or debit card authorization. Ask the customer to contact their card issuer or provide an alternate card.

Token or Cryptogram Errors

Confirm with your token provider or processor that the required token fields are included and formatted correctly in the API request.

Settlement or Reconciliation Mismatch

Compare transaction IDs, settlement batches, and processor response codes. Contact your acquirer or Authorize.net Support if you observe unexplained settlement errors.

Frequently Asked Questions

• • What is card-based debt repayment on Authorize.net?
  • Card-based debt repayment is a transaction flow that allows customers to repay a balance, loan, or other owed amount using a credit or debit card through the Authorize.net API. It uses standard card authorization and routing, with the addition of a debtRepaymentIndicator flag to identify the transaction type correctly.
• • Which processors support card-based debt repayment?
  • Currently, TSYS and First Data Nashville (FDC) support card-based debt repayment via the Authorize.net API. Virtual Terminal (VT) support for both processors is expected in Q3. If your processor is not listed, contact Authorize.net Support.
• • How do you submit a debt repayment transaction via the API?
  • Use the createTransactionRequest API call and set the debtRepaymentIndicator field to true. This is recommended for credit card bill pay, loan repayments, and certain installment payments. Confirm routing and reporting requirements with your acquirer or Authorize.net Support.
• • Is the Virtual Terminal supported for debt repayment?
  • Not yet. Virtual Terminal support is expected in Q3 for both TSYS and FDC. Currently, debt repayment is supported via the Authorize.net API only.
• • What should you do if a repayment transaction is declined?
  • A real-time decline means the card issuer declined the authorization. Ask the customer to contact their issuer or provide an alternate card. Prepare customer-facing communication templates and document alternate repayment paths in advance.
• • What should you do if you encounter token or cryptogram errors?
  • Confirm with your token provider or processor that all required token fields are included and correctly formatted in the API request. Log token and cryptogram fields securely to support troubleshooting.
• • What should you do if there is a settlement or reconciliation mismatch?
  • Compare transaction IDs, settlement batches, and processor response codes. If unexplained settlement errors persist, contact your acquirer or Authorize.net Support.
• • Does this apply to ACH or bank transfer repayments?
  • No. This article applies only to card-based debt repayment flows using credit or debit cards on the Authorize.net platform. ACH and bank transfer repayment methods are not covered here.
• • What records should you retain for repayment transactions?
  • Retain payer authorization records and repayment agreements to support reconciliation and dispute resolution. If using tokenization or digital wallets, securely log token and cryptogram fields to aid troubleshooting.

Additional Resources

• Authorize.net API Reference and Developer Guides

Appendix — Field Guidance and Definitions

debtRepaymentIndicator Field

Set debtRepaymentIndicator = true in the createTransactionRequest API call for repayment-like flows, including credit card bill pay, loan repayments, and certain installment payments. Confirm routing and reporting expectations with your acquirer before going to production.

Glossary

• ACH — Automated Clearing House: An electronic network used for financial transactions in the United States. Not applicable to this article.
• API — Application Programming Interface: A set of protocols and tools that allows software applications to communicate with each other. Debt repayment on Authorize.net is submitted via API.
• FDC — First Data Nashville: A payment processor supported for card-based debt repayment on Authorize.net.
• RAG — Retrieval-Augmented Generation: An AI approach that retrieves relevant knowledge content to generate accurate responses.
• TSYS — Total System Services: A payment processor supported for card-based debt repayment on Authorize.net.
• VT — Virtual Terminal: A web-based interface that allows merchants to process card transactions manually. VT support for debt repayment is expected in Q3.