[go: up one dir, main page]

0% found this document useful (0 votes)
15 views3 pages

Authorize API Response Guide

This document outlines the response variables for the Authorize and AuthorizeAPI methods, detailing the differences in their return formats. The AuthorizeAPI method includes a Header Record and a Response Record, while Authorize returns a single comma-delimited string. A comprehensive table lists the variable names, descriptions, types, lengths, and examples for each response variable associated with the transaction process.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views3 pages

Authorize API Response Guide

This document outlines the response variables for the Authorize and AuthorizeAPI methods, detailing the differences in their return formats. The AuthorizeAPI method includes a Header Record and a Response Record, while Authorize returns a single comma-delimited string. A comprehensive table lists the variable names, descriptions, types, lengths, and examples for each response variable associated with the transaction process.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Response Variables for Authorize and AuthorizeAPI

Methods
This section lists and describes the response variables returned for the Authorize
and AuthorizeAPI methods.

There is a slight variation in the return format for Authorize and Authorize API
transaction records. The return records are formatted as follows:

1. The AuthorizeAPI method returns a Header Record whereas the Authorize


does not. Authorize only returns a single record as a comma-delimited
name-value return string without a header record. For Authorize the
variables are listed in the table below.

2. For the AuthorizeAPI method the second record returned is the Response
Record (Data Record), containing the transaction return variables and
values listed below.

Response Variables for Authorize and AuthorizeAPI Methods

Return Variable Name Variable Description Variable Min / Example


Order Type Max
Length
1 AUTHCODE Authorization Code Numeric 0 012345
ONLY (empty)
A zero (empty field) or six- or 6
digit code identifying
whether Authorization was
Successful (Approved) or
Unsuccessful (Declined/Not
Approved) for a transaction.
2 szSerialNumbe HTML Serial Number. Numeric 12/12 000111222333
r
Skipjack-assigned unique
HTML serial number.
3 szTransactionA The purchase amount to be Numeric 3/12 500 (Five dollars)
mount authorized on the
Customer's credit card.

The return of the


TransactionAmount
variable.
4 szAuthorization A six-digit Authorization Alpha- 6/6 T12345
ResponseCode (Approval) code returned Numeric
from the cardholder's bank
(Issuer).

If the transaction is
Approved this field will
contain a six-digit string.

If the transaction is
Declined this field will
contain NULL, empty or be
empty.
5 szReturnCode Return Code generated by Numeric 1/4 See
the Skipjack Transaction and dash “szReturnCode
Network denoting whether ("-") Responses and
or not the transaction data Descriptions” for
is valid and was sent to more information.
Processor.

Returns the results of the


Validation Phase of the
Approval Process.
6 szIsApproved Single Character indicating Numeric 1/1 1, 0, or blank
the transaction results. (empty)

szIsApproved = 1 for
Approved transactions

szIsApproved = 0 for
Declined transactions

Note: This field does


not carry the AVS
filtering value.
Transactions that
show an Approval
value here may still
be Declined because
of AVS filtering.
7 szAuthorization Decline message as Alpha- 0/60 Authorization
DeclinedMessa returned from the Issuing Numeric Failed or Card
ge Bank. Declined

See also the


“Address
Verification
System” section
for more
information.
8 szAVSRespons AVS Response Code Alpha 1/1 See also the
eCode returned from the Issuing “Address
Bank. Verification
System” section
for more
information.
9 szAVSRespons Text message describing Alpha 0/60 Exact 5 digit Zip
eMessage the results of the AVS Code Match Only
Response Code.
10 szOrderNumbe Unique Order Identifier Alpha- 1/20 ABC123 or 123
r created by the ordering Numeric
application at the time the
order was generated.

Skipjack Financial Services


highly recommends that
that OrderNumber created
by your application be
unique to prevent confusion
and complications.
11 szCVV2Respo The CVV response code Alpha 1/1 See also the
nseCode returned from the “Address
cardholder’s bank. Verification
System” section
for more
information.
12 szCVV2Respo Text description of the CVV Alpha 0/60 No Match
nseMessage Response Code.
See also the
“Address
Verification
System” section
for more
information.
13 szTransactionF Unique Transaction File Numeric 10/18 9802850951761.
ileName Name (Transaction ID) and period 009
generated by the Skipjack (“.”)
Transaction Network for
each transaction.

Note that in all other


transaction methods
this is Transaction ID.
14 szCAVVRespo 3D Secure Response
nseCode

You might also like