Prior-Authorized Sale (07)

Records a previously authorized transaction for funding a (post-authorized sale) transaction. Works in conjunction with Authorization Only or Voice Authorization.

The Elavon software application assumes the authorization has already been performed, either through a voice authorization call or electronically through a previous Authorization Only (Type 01) transaction.

Prior-Authorized Sale (ends transaction life cycle) is initiated when the final purchase amount is known and the transaction is ready to be settled.

If a Prior-Authorized Sale is submitted without an Authorization Code (Field 6), the Elavon software applications go to the processor for authorization in the following instances:

  • If there is not a corresponding Authorization Only transaction in the Elavon Gateway application database.
  • If the Auto Authorize Difference flag within the Elavon Gateway application is set to Yes and the final amount is outside the authorized total tolerance amount set for the industry.
  • If a Prior-Authorized Sale is processed with an Authorization Code (Field 6) number and does not have a matching authorization in the Elavon Gateway applications database (same reference number, Token (Unique ID) or cardholder account number, and Elavon Gateway Terminal ID), the transaction is treated as a forced sale or voice authorization and is added to the Elavon Gateway applications database.

note

By tracking the Elavon Token or Unique ID, from the original Authorization, the Prior Authorized Sale does not require the cardholder account number.

Example of a prior authorized sale transaction. Partial authorization acceptance with approved original amount.

Request

0001,07<– Transaction Type –>
0002,2,50<– Transaction Amount –>
0003,ID:7234561234561865<– Card Number, Token or Unique ID –>
0004,1220<– Credit Card Expiration Date MMYY –>
0006,000018<– Approval Code (From Original Authorization) –>
0007,13455<– Reference Number –>
0025,030120<– Business Date –>
0052,0<– Transponder and Proximity Indicator –>
0060,00000001< – Unique Device ID –>
0070,1111ABC<– Customer Code –>
0071,1<– Tax1 Indicator –>
0072,1.00<– Tax Amount 1 –>
0109,TERM1<–Terminal ID–>
0110,105<–Cashier ID–>
0115,010<–Transaction Qualifier–>
*Industry Data<–The proper industry data would be supplied and the example is left out–>
0647,1<–Partial Authorization Acceptance–>
1105,DOCID:12345678901<– Global User Defined Field –>
5002,123456<–Device Serial Number–>
8002,LOC1<–Location Name–>
8006,CHAIN<–Chain Code–>

Response

0001,01<–Transaction Type–>
0002,2,50<–Transaction Amount–>
0003,ID:7234561234561865<–Card Number, Token or Unique ID–>
0004,1220<–Credit Card Expiration Date MMYY –>
0006,000018<–Approval Code (From Original Authorization)–>
0007,13455<–Reference Number–>
0009,0010<–Host Batch Number–>
0025,030120<–Business Date MMYY–>
0030,1<–Online Indicator–>
0032,030120<–Authorization Transaction Date MMDDYY–>
0033,083518<–Authorization Transaction Time HHMMSS–>
0034,E<–Authorizations Characteristics Identifier –>
0035,0100<– Validation Code–>
0036,001234567810100<–Transaction Identifier–>
0037,5<–Authorizer–>
0038,00<–Reason Code–>
0043,101910<–System Trace Audit Number–>
52,0<–Transponder and Proximity Indicator–>
60,00000001<–Unique Device ID–>
0070,1111ABC<–Customer Code–>
0071,1<–Tax1Indicator –>
0072,1.00<–Tax Amount 1–>
109,TERM1<–Terminal ID–>
0110,105<–Cashier ID–>
0115,010<–Transaction Qualifier–>
0126,0<–Track Indicator–>
0128,2.50<–Original Authorization Amount–>
0130,2.50<–Total Authorization Amount–>
0131,<–Total Incremental Authorizations Sent–>
The proper industry data would be supplied and the example left out.<–Industry Data –>
0647,1<–Partial Authorization Acceptance–>
1000,VI<–Card Type–>
1001,VISA<–Card Name–>
1004,AP<–Final Four Host Response Message–>
1005,7993241<–Merchant Number–>
1008,401288*****1865<–Masked Account Number–>
1009,000<–Host Response Code–>
1020,A<–AVS Response Code–>
1105,DOCID:12345678901<– Global User Defined Field–>
5002,123456<–Device Serial Number–>
7007,12345678901234567<–Fusebox Transaction Identifier–>
8002,LOC1<–Location Name–>
8006,CHAIN<–Chain Code–>

note

  • Never present swipe data when completing an authorization because the POS application is not allowed to retain swipe data during the transaction life-cycle.
  • Partial Authorization (647=1) is not recommended for life-cycle transactions. If prior authorized sales are not completed while the customer is still present, there will not be an opportunity to obtain another form of payment to complete the POS transaction.
  • Partial Authorization Acceptance should not apply to a voice authorization because the entire amount was authorized in the voice auth.

Voice Authorization

Example of a “voice” prior authorized sale transaction with partial authorization acceptance not allowed, original amount requested approved.

Request

0001,07<–Transaction type–>
0002,2.50<–Transaction Amount–>
0003,4012XXXXXXXX1865<–Card Number, Token or Unique ID–>
0004,1220<–Credit Card Expiration Date MMYY–>
0006,000018<–Approval Code–>
0007,13455<–Reference Number–>
0025,030120<–Business Date MMDDYY–>
0052,0<–Transponder and Proximity Indicator–>
0060,00000001<–Unique Device ID–>
0070,1111ABC<–Customer Code–>
0071,1<–Tax1 Indicator–>
0072,1.00<–Tax Amount 1–>
0109,TERM1<–Terminal ID–>
0110,105<–Cashier ID–>
0115,010<–Transaction Qualifier–>
*Industry Data<–The proper industry data would be supplied and the example is left out.–>
0647,0<–Partial Authorization Acceptance–>
1008,ID:<–Requests Token or Unique ID in Input
Request Masked Account Number in Output Response–>
1105,DOCID:12345678901<–Global User Defined Field–>
5002,123456<–Device Serial Number–>
8002,LOC1<–Location Name–>
8006,CHAIN<–Chain Code–>

Response

0001,01<–Transaction type–>
0002,2.50<–Transaction Amount–>
0003,ID:7234561234561865<–Card Number, Token or Unique ID–>
0004,1220<–Credit Card Expiration Date MMYY–>
0006,000018<–Approval Code–>
0007,13455<–Reference Number–>
0025,030120<–Business Date MMDDYY–>
0030,0<–Online Indicator–>
0032,030120<–Authorization Transaction Date MMDDYY–>
0033,083518<–Authorization Transaction Time HHMMSS–>
52,0<–Transponder and Proximity Indicator–>
60,00000001<–Unique Device ID–>
0070,1111ABC<–Customer Code->
0071,1<–Tax1 Indicator–>
0072,1.00<–Tax Amount 1–>
0109,TERM1<–Terminal ID–>
0110,105<–Cashier ID–>
0115,010<–Transaction Qualifier–>
0126,0<–Track Indicator–>
0128,2.50<–Original Authorization Amount–>
0130,2.50<–Total Authorized Amount–>
0131,<–Total Incremental Authorizations Sent
The proper industry data would be supplied and this example is left out.<–Industry Data–>
0647,0<–Partial Authorization Acceptance–>
1000,VI<–Card Type–>
1001,VISA<–Card Name–>
1004,AP<–Final Four Host Response Message–>
1005,7993241<–Merchant Number–>
1008,401288*****1865<–Requests Token or Unique ID in Input. Request Masked Account Number in Output Response–>
1009,000<–Host Response Code–>
1105,DOCID:12345678901<–Global User Defined Field–>
5002,123456<–Device Serial Number–>
7007,12345678901234567<–Fusebox Transaction Identifier–>
8002,LOC1<–Location Name–>
8006,CHAIN<–Chain Code–>