Also called: Auth code, Approval code, Credit card authorization code, Validation code
What an authorization code is
When you submit a card transaction for approval, the issuer returns an authorization decision. For an approved transaction, the response includes an authorization code, a six-character reference tied to that approval. Your processor passes the result back to your payment system or terminal.
The code is not the same as Authorization, which is the approval decision and process. It is also different from a response code, such as 00 for an approval or 05 for a decline. Those response codes describe the outcome; the authorization code identifies the approved transaction.
An authorization code identifies an approval, but it does not prove that the sale was captured or paid.
How the code is used
The issuer makes the decision after receiving the transaction request through the processing chain. If approved, your terminal, gateway, or processing software stores the authorization code with the transaction record. The code can help you find the transaction when reviewing a sale, refund, or customer inquiry.
Approval is a preliminary step. You still need to capture the transaction and have it cleared before it is included in settlement and funds are paid to your business. A code alone does not prove that capture or settlement happened, and it does not prevent a later dispute.
What it means for your costs and records
The authorization code is a transaction reference, not one of the three card-cost layers: interchange, network fees, or processor markup. It does not set those rates or guarantee that an approved sale will be funded. The code itself does not tell you whether your processor charged for the transaction.
You might see the code in a transaction-detail view or receipt, but there is no single statement line name established for it. Match the code to the transaction date, amount, and transaction ID in your payment records. That gives you a clearer trail if a sale is missing from a batch or a customer asks about a charge.
What you can actually change
You cannot control the code the issuer returns. You can control whether your records connect the approval to capture and settlement, so an approval does not get mistaken for completed payment.
- Keep the authorization code with the transaction record, amount, and transaction ID.
- Track approved transactions through capture, clearing, and settlement.
- Reconcile approved transactions against captured sales and your settled batch.
- Treat response codes and authorization codes as different fields when reviewing transaction details.
- Match transaction records. Use the authorization code alongside the transaction ID, date, and amount to locate a specific approved sale.
- Confirm capture. Compare approved sales with captured transactions so an approval does not get mistaken for completed processing.
- Reconcile settled batches. Check that captured sales appear in the batch that was sent for settlement.
Frequently asked questions
Is an authorization code proof that I have been paid?
No. The code identifies an approved card transaction, but approval is preliminary. You still need to capture the transaction and have it cleared before it is included in settlement and funds are paid to your business.
Is an authorization code the same as a response code?
No. A response code communicates the transaction outcome, such as 00 for approval or 05 for decline. The authorization code is the six-character reference associated with an approved transaction.
Where can I find an authorization code?
Look in the transaction details in your terminal, gateway, or processing software. The code is stored with the transaction record, but there is no single statement line name that applies to every processor.