Appendix A

Sample Reply Data and Receipts

Topics covered in this appendix:

Reply Data

Transaction Receipts

Reply Data

Examples in this section:

Successful Order

Order to Review

Failed Order

These examples apply to you only if you customize your order, receipt, and decline pages. When reviewing orders, examine these fields to decide whether to accept, review, or reject an order:

•   The decision field provides the overall decision for the order: accept, review, or reject.

•   The reasonCode field provides the reason code for the order and the recommended action associated with the code. Reason codes are described in this page.

You can receive at a URL or email address the same data that you receive in the reply.

Successful Order

This reply shows a successful card transaction. In this case, the customer receives the reply page for a successful order. These elements are highlighted:

•   Factor code U means that the address cannot be verified.

•   AVS code X means that the street address and the 9-digit code match.

•   Reason code 100 and the decision mean that the order is accepted.

•   transactionSignature and signedFields are used by the verify transaction signature function to verify the contents of the order.

merchantID=example

requestID=1117778322620167904543

orderPage_requestToken=ZLzrfOnKPFoWy2P6rGgok4gHIaeLSZ0br

billTo_firstName=John

billTo_lastName=Doe

billTo_street1=123 HAPPY LANE

billTo_city=San Francisco

billTo_state=CA

billTo_country=us

billTo_postalCode=94133

billTo_email=jdoe@example.com

ccAuthReply_authFactorCode=U

ccAuthReply_avsCode=X

ccAuthReply_amount=10.00

ccAuthReply_authorizationCode=888888

ccAuthReply_authorizedDateTime=2005-03-25T191034Z

ccAuthReply_reasonCode=100

ccAuthReply_reasonCode=100

reasonCode=100

decision=ACCEPT

decision_publicSignature=aEFRvKdMUCwa5JguMZ8LGfwGczE=

orderAmount=10.00

orderAmount_publicSignature=VpqNi+pZpwqpGztckBfunTQwLT0=

orderNumber=1111777830935

orderNumber_publicSignature=piWfSvHR1gGgfteZVgjBMfGSe8U=

orderPage_transactionType=authorization

paymentOption=credit

card_cardType=001

card_cardNumber=xxxx

card_expirationMonth=11

card_expirationYear=2008

transactionSignature= APooM70Mkl15OAeOeNMsc280Tts=

signedFields=merchantID,requestID,orderPage_requestToken,billTo_firstName,billTo_lastName, billTo_street1,billTo_city,billTo_state,billTo_country,billTo_postalCode,billTo_email, ccAuthReply_authFactorCode,ccAuthReply_amount,ccAuthReply_authorizationCode, ccAuthReply_authorizedDateTime,ccAuthReply_avsCode,ccAuthReply_reasonCode,reasonCode, decision,decision_publicSignature,orderAmount,orderAmount_publicSignature,orderNumber, orderNumber_publicSignature,orderPage_transactionType,paymentOption,card_cardType, card_cardNumber,card_expirationMonth,card_expirationYear

Payer Authentication

With Payer Authentication with an enrolled Visa card (subsequently validated), the reply for a successful authorization includes data similar to this:

  proofXML=<AuthProof><Time>2007 Jul 26 09:04:53</Time><DSUrl>https:111.111.36:443/DSMsgServlet </DSUrl><VEReqProof><Message id="xfm5_3_0.269"><VEReq><version>1.0.2</version><pan> XXXXXXXXXXXX0771</pan><Merchant><acqBIN>123456</acqBIN><merID>8768516</merID></Merchant> <Browser><accept>text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8, image/png,*/*;q=0.5</accept><userAgent>Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.5) Gecko/20070713 Firefox/2.0.0.5</userAgent></Browser></VEReq></Message></VEReqProof> <VEResProof><Message id="xfm5_3_0.269"><VERes><version>1.0.2</version><CH><enrolled>Y</enrolled> <acctID>NDAxMjsocTAxMTAwMDc3MQ==</acctID></CH><url>https://www.littletooth.com/verification/appl/pareq.php?vaa=a</url><protocol>ThreeDSecure</protocol></VERes></Message></VEResProof></AuthProof>

xid=8okfADuvn038vn7MOPfIzMwAHBwE=

eci=05

cavv=AAAAAAAAAAAAAAAAAAAAAAAAAAA=

Order to Review

CyberSource directs the customer to the receipt page for accepted orders for all successful orders and for orders declined by Smart Authorization. In the search results page and in the reply, these orders are marked Review. By default, replies that contain these reason codes are marked for review:

•   200: The authorization request was approved by the issuing bank but declined by CyberSource because it did not pass the Address Verification Service (AVS) check.

•   201: The issuing bank has questions about the request. You cannot receive an authorization code in the API reply, but you may receive one verbally by calling the bank.

•   230: The credit card was accepted by the bank but refused by CyberSource because it did not pass the card verification number check. The card verification result is N.

•   520: The authorization request was approved by the issuing bank but declined by CyberSource based on your Smart Authorization settings.

However, if you customize your implementation to choose the page that your customers receive, the reason code(s) that trigger a review for your orders may differ from those that are described above.

Request

In this example, CyberSource receives this transaction information from the your Web site:

Merchant ID

Example

 

Customer’s billing information

first name

last name

street address 1

city

state

country

postal code

email address

 

John

Doe

123 Happy Lane

San Francisco

CA

US

94133

jdoe@example.com

 

Shipping information

first name

last name

street address 1

city

state

country

postal code

 

Jane

Doe

456 Elm Street

Mountain View

CA

us

94066

Reply

Because the billing and shipping addresses do not match, the merchant would receive this reply from CyberSource:

merchantID=example

requestID=9996668322620167904543

orderPage_requestToken=44vglD3VtqcYgHgT0yV3llPKrNaQah4G2

ccAuthReply_authFactorCode=J^U

ccAuthReply_amount=10.00

ccAuthReply_authorizationCode=888888

ccAuthReply_authorizedDateTime=2005-03-25T191034Z

ccAuthReply_avsCode=Y

ccAuthReply_reasonCode=520

reasonCode=520

decision=REVIEW

decision_publicSignature=aEFRvKdMUCwa5JguMZ8LGfwGczE=

orderAmount=10.00

orderAmount_publicSignature=VpqNi+pZpwqpGztckBfunTQwLT0=

orderNumber=1111777830935

orderNumber_publicSignature=piWfSvHR1gGgfteZVgjBMfGSe8U=

orderPage_transactionType=authorization

paymentOption=credit

card_cardType=001

card_cardNumber=xxxx

card_expirationMonth=11

card_expirationYear=2008

transactionSignature=APooM70Mkl15OAeOeNMsc280Tts=

signedFields=<comma-separated list of all the data fields in the order>

Factor codes U and J mean that the billing and shipping addresses do not match.

Reason code 520 means that the order failed the Smart Authorization tests.

The decision field indicates that you should review the order.

Failed Order

Most transactions that cannot be accepted are rejected, and the customer receives the reply page for a failed order. However, if you customized your implementation to choose the page that your customers receive, the reason code(s) that trigger a rejection for your orders may differ from the CyberSource defaults.

The samples below show excerpts for transactions in which the credit card is either declined (203) or missing (102).

Invalid field reply

Missing field reply

decision=REJECT

reasonCode=203

decision=REJECT

reasonCode=102

MissingField0=card_expirationYear

Transaction Receipts

The following two receipts are formatted as memos. You do not specify the content, except for the header and the footer. Receipts in this section:

Customer’s Receipt

Merchant’s Receipt

Customer’s Receipt

The customer’s receipt shows the payment information with only the last four digits of the credit card number.

From: merchant@sample.com [mailto:merchant@sample.com]

Sent: Wednesday, May 25, 2005 12:42 PM

To: Doe, Jane

Subject: Purchase Confirmation

 

Purchase Description

  Widget

 

Payment Details

  Order Number:           12345

  Subtotal:               30.00

  Tax:                     0.00

  Total:                  30.00

 

Order Details

  Payment Option:         card

  Card Description:       Visa ############1111

 

  Customer ID:

  Bill Address:

  123 Anystreet

  Mountain View, California 94043

 

If you have questions about your order, please contact service@example.com.

Merchant’s Receipt

This receipt shows an enrolled card transaction with Visa and Payer Authentication. Because the card is not enrolled, validation does not occur, and the enrollment check is followed by the authorization.

From: Cybersource [mailto:sample@cybersource.com]

Sent: Friday, June 10, 2005 3:13 PM

To: Merchant, Sample

Subject: Purchase Confirmation

 

Purchase Description

  Widget

Payment Details

  Order Number:           12345

  Subtotal:               30.00

  Tax:                     0.00

  Total:                  30.00

Return Codes

  Result Code:            Request was processed successfully.

  Auth Code:              888888

  AVS Code:               X

  CVN Code:

 

Transaction Details

  Transaction Type:       sale

  Transaction Source:     Hosted Order Page

  Payment Option:         card

  Card Description:       Visa ############1111

  Request Token:          H7v9JeVSuzD3YtvP6hIPeU3wN0dvJy16RC9GRH8Y

 

Payer Authentication

  proofXML=<AuthProof><Time>2007 Jul 26 09:04:53</Time><DSUrl>https:111.111.111.36:443/DSMsgServlet</DSUrl><VEReqProof><Message id="xfm5_3_0.269"><VEReq><version>1.0.2</version><pan> XXXXXXXXXXXX0771</pan><Merchant><acqBIN>123456</acqBIN><merID>8768516</merID></Merchant> <Browser><accept>text/xml,application/xml,application/xhtml+xml,text/html;q=0.9, text/plain; q=0.8,image/png,*/*;q=0.5</accept><userAgent>Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.5) Gecko/20070713 Firefox/2.0.0.5</userAgent></Browser></VEReq></Message></VEReqProof> <VEResProof><Message id="xfm5_3_0.269"><VERes><version>1.0.2</version><CH><enrolled>Y</enrolled> <acctID>NDAxMjsocTAxMTAwMDc3MQ==</acctID></CH><url>https://www.littletooth.com/verification/appl/pareq.php?vaa=a</url><protocol>ThreeDSecure</protocol></VERes></Message></VEResProof></AuthProof>

  eci=06

 

Customer Information

  Bill Address:

  123 Anystreet

  Mountain View, California 94043

 

Merchant-Defined Data

  Field 3:                Express shipping

If you have questions about your order, please contact service@example.com.