What a referral code is
In this card-processing context, Referral is an operation for resubmitting an initial transaction that received a "Refer to Issuer" response. You obtain an authorization code from the issuer and include it in a new authorization or Pay request. The code is generated by the issuer, not by your business.
This is different from a customer referral-promotion code, which tracks who recommended a new buyer. A payment referral code belongs to an authorization workflow, not a marketing discount.
A referral response is not an approval, and the issuer's code is used for a new payment request.
How the referral process works
The initial response means the transaction was declined and should be referred to the issuer. In one documented API, the gateway result appears as `REFERRED`. After obtaining the issuer's authorization code, you submit a new Authorization or Pay transaction rather than treating the first request as approved.
The request includes the authorization code in `transaction.authorizationCode`. The documented field accepts 1 to 6 letters or numbers. The request also includes a transaction ID, and each retry must use a new, unique transaction ID.
How it differs from a response code
A response code reports the result or next step for a payment attempt. A referral code, in this workflow, is the issuer-provided authorization code used in the follow-up request. The two values do different jobs: one directs you to the issuer, and the other is supplied by the issuer for a new attempt.
A referral result does not mean the sale has been approved, captured, or settled. Treat it as a prompt to follow the issuer referral process, then confirm the result of the new request before considering the payment complete.
What it means for your costs
The documented referral operation does not specify a referral fee, a processing-time limit, or a separate statement line. The code itself is an authorization value, not a stated fee amount. If your statement has a charge labeled "referral," evaluate that charge by its actual line name and amount rather than assuming the authorization code explains it.
What you can actually change
You do not set the issuer's authorization code or turn a referral response into an approval. You can keep the follow-up request accurate and avoid mistaking an unresolved referral for a completed sale.
- Record the initial response and obtain the authorization code from the issuer before resubmitting.
- Send the follow-up as a new Authorization or Pay request with the required authorization code.
- Use a new, unique transaction ID for every retry and confirm its response before recording the payment as complete.
- Review any statement charge labeled "referral" as a separate processor fee, not as the issuer's code.
- Verify the result. Keep the initial referral response separate from the outcome of the follow-up authorization or Pay request.
- Match the required fields. For an API resubmission, confirm the issuer's code is in `transaction.authorizationCode` and the request has a unique transaction ID.
- Separate fees from codes. If a referral-related charge appears on your statement, identify the exact fee label and amount before treating it as a processing cost.
Frequently asked questions
Does a referral code mean the card payment was approved?
No. A "Refer to Issuer" result means the initial transaction was declined and referred to the issuer. The issuer's authorization code is used in a new Authorization or Pay request, and you must confirm that request's result.
Is a referral code the same as a response code?
No. A response code communicates a payment result or next step. In this workflow, the referral code is the authorization code supplied by the issuer for a new payment request.
Is a referral code a fee on my processing statement?
The documented referral workflow describes an issuer-provided authorization code, not a fee amount or statement line. If your statement lists a referral-related charge, assess it by the exact line label and amount.