Afterpay and Clearpay Services

Options

Use the options service to request the minimum amount, maximum amount, and currency for the day from your Afterpay and Clearpay account.

Endpoints

Set the
apOptionsService_run
field to
true
, and send the request to one of these endpoints:
Production:
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
Test:
https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor

Example: Options Service with XML

Create a Session

Creating a session is mandatory for processing a payment. To create a session, you must include shipping fields in your request. The shipping field values are included in the invoice Afterpay and Clearpay send to the customer.
A successful session response includes an Afterpay or Clearpay redirect URL and a token. Send the customer to the redirect URL to approve the payment using their Afterpay or Clearpay account. Use the token in the authorization request to link the authorization to the session.

Endpoints

Set the
apSessionsService_run
field to
true
, and send the request to one of these endpoints:
Production:
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
Test:
https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor

Response Status

The session service responds with this status as the
apSessionReply_status
field value:
  • PENDING
    : The Afterpay or Clearpay redirect URL is generated. Redirect the customer to the Afterpay or Clearpay URL.
The session service also responds with a reason code as the
apSessionReply_reasonCode
field value. For more information about reason codes, see the Reason Codes for the Simple Order API.

Line Items

Afterpay and Clearpay use optional line item fields when you send a session request.
Line items are used to include information about the goods that your customers purchase, such as product name, quantity, and price.
Line items are represented as the
item_#_
fields, starting with
item_0_
, and increasing in numerical order.
These fields are required for each line item that you use:
Including Line Items
This example shows three valid line items.
<item id="0"> <unitPrice>20</unitPrice> <quantity>1</quantity> <productCode>98765</productCode> <productName>shirt</productName> <productSKU>testJ</productSKU> <totalAmount>20</totalAmount> </item> <item id="1"> <unitPrice>10</unitPrice> <quantity>3</quantity> <productCode>65432</productCode> <productName>pants</productName> <productSKU>testK</productSKU> <totalAmount>30</totalAmount> </item> <item id="2"> <unitPrice>5</unitPrice> <quantity>5</quantity> <productCode>12345</productCode> <productName>socks</productName> <productSKU>testX</productSKU> <totalAmount>25</totalAmount> </item>

Creating a Session

Follow these steps to successfully complete a session request.
  1. Include any of these optional fields in the request:

    ADDITIONAL INFORMATION

    apSessionService_paymentMethod_name
    Set to
    N
    .
    billTo_street2
    Replace the
    #
    character with a sequential number starting from
    0
    .
    Replace the
    #
    character with a sequential number starting from
    0
    .
    Replace the
    #
    character with a sequential number starting from
    0
    .
    Replace the
    #
    character with a sequential number starting from
    0
    .
    Replace the
    #
    character with a sequential number starting from
    0
    .
    Replace the
    #
    character with a sequential number starting from
    0
    .
    When this field is included in the request, the
    purchaseTotals_grandTotalAmount
    field is no longer required.
    Replace the
    #
    character with a sequential number starting from
    0
    .
  2. Store the value in the
    processorToken
    field from the session response. You must include this value in the follow-on authorization request.

    ADDITIONAL INFORMATION

    <processorToken>
    5f97d636-85d1-486b-a1de-96111938ec61
    </processorToken>
  3. Redirect the customer to the returned Afterpay or Clearpay URL contained in the
    merchantURL
    response field.

    ADDITIONAL INFORMATION

    <merchantURL>
    https://portal.afterpay.com/us/checkout/?token=002.suuh2tq1gfvthg0180il0928fjkhg1p4ufg4savhihcvm9uj
    </merchantURL>
  4. When the customer completes the checkout using their Afterpay or Clearpay credentials, Afterpay or Clearpay redirects the customer to the success URL specified in the session request. You can now send an authorization request.
  5. When you send the authorization request, set the
    apAuthService_preapprovalToken
    field to the
    processorToken
    field value you stored from the session response.

Simple Order API
Example: Create Session with XML

Simple Order API
Example: Create Session Using Line Items with XML

Authorizations

Use the authorization service to process a payment request to Afterpay or Clearpay. You must include the token received from the session response in the authorization request to receive a successful response.

Endpoints

Set the
apAuthService_run
field to
true
, and send the request to one of these endpoints:
Production:
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
Test:
https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor

Response Status

An authorization can have one of the following statuses:
  • AUTHORIZED
    : the payment is authorized.
  • PENDING
    : the authorization request is accepted, but the payment is not authorized. To authorize the payment, complete the authorization using the payment redirection URL that you received in the authorization response.
  • FAILED
    : the authorization request fails when there are invalid or missing fields.

Optional Fields for Authorizing a Payment

Choose from these optional fields to include in the authorization request.
apAuthService_reconciliationID
Set to the
reconciliationID
returned in the session response.
Replace the
#
character with a sequential number starting from
0
.
Replace the
#
character with a sequential number starting from
0
.
Replace the
#
character with a sequential number starting from
0
.
Replace the
#
character with a sequential number starting from
0
.
Replace the
#
character with a sequential number starting from
0
.
If this field is present, the
purchaseTotals_grandTotalAmount
field becomes optional.
Replace the
#
character with a sequential number starting from
0
.
Replace the
#
character with a sequential number starting from
0
.
Set to
inline
.

Example: Authorizing a Payment with XML

These examples show successful authorization requests.

Captures

Use this service to capture an authorized payment. Partial captures and full-amount captures are both supported.

Endpoints

Set the
apCaptureService_run
field to
true
, and send the request to one of these endpoints:
Production:
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
Test:
https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor

Response Status

The capture service responds with one of these statuses as the
apCaptureReply_status
response field value:
  • FAILED
    : The capture request failed.
  • PENDING
    : The capture request is accepted but is not captured. Request the check status service to retrieve status updates.
  • SETTLED
    : The capture request is settled for the requested amount.
The capture service also responds with a reason code as the
apCaptureReply_reasonCode
field value.

Required Fields for Capturing an Authorization

Example: Capturing an Authorization with XML

Sales

This service enables you to send both a payment authorization request and a capture request as a single transaction using the sale service. You must include the token received from the session response in the sale request to receive a successful response.

Endpoints

Set the
apSaleService_run
field to
true
, and send the request to one of these endpoints:
Production:
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
Test:
https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor

Response Status

A sale request can have one of the following statuses:
  • FAILED
    : the sale request fails when there are invalid or missing fields.
  • PENDING
    : the sale request is accepted but is not settled. To settle the payment, check out using the payment redirect URL that you received in the sale response.
Once
SETTLED
, a sale transaction cannot be reversed using the authorization-reversal service. You must use a credit request to refund a transaction.

Optional Fields for a Sale

Replace the
#
character with a sequential number starting from
0
.
Replace the
#
character with a sequential number starting from
0
.
Replace the
#
character with a sequential number starting from
0
.
Replace the
#
character with a sequential number starting from
0
.
Replace the
#
character with a sequential number starting from
0
.
Replace the
#
character with a sequential number starting from
0
.
When this field is included in the request, the
purchaseTotals_grandTotalAmount
field is no longer required.
Replace the
#
character with a sequential number starting from
0
.

Example: Performing a Sale with XML

Refunds

Send a refund request to credit a
SETTLED
capture. A refund request requires the request ID and reconciliation ID returned in the capture response.

Endpoints

Set the
apRefundService_run
field to
true
, and send the request to one of these endpoints:
Production:
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
Test:
https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor

Response Status

The refund service responds with one of these statuses as the
apRefundReply_status
field value:
  • FAILED
    : The refund request failed.
  • PENDING
    : The refund request is accepted but is not refunded. Request the check status service to retrieve status updates.
  • REFUNDED
    : The captured payment is successfully refunded.
The refund service also responds with a reason code as the
apRefundReply_reasonCode
field value.

Example: Refunding a Payment with XML

Authorization-Reversals

Use this service to reverse an unnecessary or undesired authorization.

Endpoints

Set the
apAuthReversalService_run
field to
true
, and send the request to one of these endpoints:
Production:
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
Test:
https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor

Response Status

The authorization reversal service responds with one of these statuses as the
apAuthReversalReply_status
field value:
  • AUTH_REVERSED
    : The authorization is successfully reversed.
  • FAILED
    : The authorization reversal failed.
The authorization reversal service also responds with a reason code as the
apAuthReversalreply_reasonCode
field value.

Required Fields for Reversing an Authorization

Include these required fields in the authorization-reversal request.

Example: Reversing an Authorization with XML

Check Status

This service returns the current status of an Afterpay or Clearpay transaction. Use the request ID value returned by the individual service to check the status of the service request.

Endpoints

Set the
apCheckStatusService_run
field to
true
, and send the request to one of these endpoints:
Production:
https://ics2ws.ic3.com/commerce/1.x/transactionProcessor
Test:
https://ics2wstest.ic3.com/commerce/1.x/transactionProcessor

Response Status

The check status service returns one of the following statuses:
  • AUTHORIZED
    : you have successfully completed the authorization or sale using the redirection URL sent in response.
  • AUTH-REVERSED
    : the authorization is successfully reversed.
  • FAILED
    : the service request is rejected due to missing fields, invalid fields, or downtime.
  • PENDING
    : the payment is waiting for authentication or approval. When you receive a pending status, wait a short time and request the check status service.
  • REFUNDED
    : the refund is successfully completed.
  • SETTLED
    : the payment is successfully completed.

Example: Checking Status with XML

Light Dark
Request
123456789
<="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantID>test_merchant</merchantID> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <apPaymentType>afp</apPaymentType> <apOptionsService run="true"> <limit>3</limit> <offset>2</offset> </apOptionsService> </>
Response to a Successful Request
12345678910111213141516171819202122232425262728293031323334353637
<:c="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantReferenceCode>123456</merchantReferenceCode> <requestID>6246005374346859304083</requestID> <decision>ACCEPT</decision> <reasonCode>100</reasonCode> <apOptionsReply> <reasonCode>100</reasonCode> <responseCode>00000</responseCode> <offset>0</offset> <count>6</count> <totalCount>6</totalCount> <option data="0"> <id>6</id> <name>1000.00</name> </option> <option data="1"> <id>5</id> <name>Maximum Amount</name> </option> <option data="2"> <id>4</id> <name>1.00</name> </option> <option data="3"> <id>3</id> <name>Minimum Amount</name> </option> <option data="4"> <id>2</id> <name>USD</name> </option> <option data="5"> <id>1</id> <name>Currency</name> </option> </apOptionsReply> </>
Light Dark
Request
1234567891011121314151617181920212223242526272829303132
<="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantID>test_merchant</merchantID> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <billTo> <firstName>John</firstName> <lastName>Smith</lastName> <street1>Happy</street1> <city>Austin</city> <state>TX</state> <postalCode>78757</postalCode> <country>US</country> <email>test@cybs.com</email> </billTo> <shipTo> <firstName>John</firstName> <lastName>Smith</lastName> <street1>Happy</street1> <city>Austin</city> <state>TX</state> <postalCode>78757</postalCode> <country>US</country> </shipTo> <purchaseTotals> <currency>USD</currency> <grandTotalAmount>600</grandTotalAmount> </purchaseTotals> <apPaymentType>AFP</apPaymentType> <apSessionsService run="true"> <cancelURL>https://www.test0.com</cancelURL> <successURL>https://www.test1.com</successURL> </apSessionsService> </>
Response to a Successful Request
1234567891011121314151617181920
<:c="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <requestID>6951825944986489403007</requestID> <decision>ACCEPT</decision> <reasonCode>100</reasonCode> <requestToken>AxjnrwSTeNv3IJzf8zZ/AAUZYjWmrWbQcsYsOgojmhl/H/SCHUwGX0MmkmXoxZaH/pN42/cgnN/zNn8A2VlF</requestToken> <purchaseTotals> <currency>USD</currency> </purchaseTotals> <apSessionsReply> <reasonCode>100</reasonCode> <responseCode>00000</responseCode> <merchantURL>https://portal.sandbox.afterpay.com/us/checkout/?token=002.suuh2tq1gfvthg0180il0928fjkhg1p4ufg4savhihcvm9uj</merchantURL> <processorToken>519ff272-d850-4c81-ab65-674f670063c7</processorToken> <amount>600.00</amount> <reconciliationID>XFZ55MP91ECP</reconciliationID> <status>COMPLETED</status> <dateTime>2023-09-20T04:03:14Z</dateTime> </apSessionsReply> </>
Light Dark
Request with Optional Line Items
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
<="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantID>test_merchant</merchantID> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <billTo> <firstName>John</firstName> <lastName>Smith</lastName> <street1>Peachtree St</street1> <city>Atlanta</city> <state>GA</state> <postalCode>33019</postalCode> <country>US</country> <email>test@cybs.com</email> </billTo> <shipTo> <firstName>John</firstName> <lastName>Smith</lastName> <street1>Peachtree St</street1> <city>Atlanta</city> <state>GA</state> <postalCode>30319</postalCode> <country>US</country> </shipTo> <item id="0"> <unitPrice>1</unitPrice> <quantity>10</quantity> <productCode>4564</productCode> <productName>TV</productName> <productSKU>testI</productSKU> <totalAmount>10</totalAmount> </item> <item id="1"> <unitPrice>15</unitPrice> <quantity>1</quantity> <productCode>65432</productCode> <productName>TV</productName> <productSKU>testJ</productSKU> <totalAmount>15</totalAmount> </item> <purchaseTotals> <currency>USD</currency> </purchaseTotals> <apPaymentType>AFP</apPaymentType> <apSessionsService run="true"> <cancelURL>https://www.test.com</cancelURL> <successURL>https://www.test1.com</successURL> <paymentMethod_name>afp</paymentMethod_name> </apSessionsService> </>
Response with Optional Line Items
1234567891011121314151617181920
<:c="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <requestID>6977376246486503703007</requestID> <decision>ACCEPT</decision> <reasonCode>100</reasonCode> <requestToken>AxjnrwSTej6MCHSsbsHfAAUZYiy6ladJo2qFOEnkFtpem2kDJxDNyGTSTL0YwW2Lkm9H0YEOlY3YO+AAES2i</requestToken> <purchaseTotals> <currency>USD</currency> </purchaseTotals> <apSessionsReply> <reasonCode>100</reasonCode> <responseCode>00001</responseCode> <merchantURL>https://portal.sandbox.afterpay.com/us/checkout/?token=002.kfl0qoc9q5tarv41p34s1dvbrk62iflv382j1sd0ot7o5s82</merchantURL> <processorToken>0d97aa1b-a9dd-4e9c-b60c-b1157470d034</processorToken> <amount>25.00</amount> <reconciliationID>XEKTVNIQZPSB</reconciliationID> <status>PENDING</status> <dateTime>2023-10-19T17:47:05Z</dateTime> </apSessionsReply> </>
Light Dark
Request
123456789101112131415161718192021222324252627282930313233
<="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantID>test_merchant</merchantID> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <billTo> <firstName>John</firstName> <lastName>Smith</lastName> <street1>123 Happy St</street1> <city>Austin</city> <state>TX</state> <postalCode>78757</postalCode> <country>US</country> <email>test@cybs.com</email> </billTo> <shipTo> <firstName>John</firstName> <lastName>Smith</lastName> <street1>123 Happy</street1> <city>Austin</city> <state>TX</state> <postalCode>78757</postalCode> <country>US</country> </shipTo> <purchaseTotals> <currency>USD</currency> <grandTotalAmount>75.00</grandTotalAmount> </purchaseTotals> <apPaymentType>afp</apPaymentType> <apAuthService run="true"> <cancelURL>https://www.test.com</cancelURL> <successURL>https://www.test.com</successURL> <preapprovalToken>519ff272-d850-4c81-ab65-674f670063c7</preapprovalToken> </apAuthService> </>
Response to a Successful Request
123456789101112131415161718192021
<:c="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <requestID>6246274241256683803069</requestID> <decision>ACCEPT</decision> <reasonCode>100</reasonCode> <requestToken>AxjnrwSTeaOOe5Ed6nFKAAUZYjWmrWdFqOaFmiojml/qNzSBvUwzPhk0ky9GMFti5JvNHHPciO9TilAA4hjb</requestToken> <purchaseTotals> <currency>USD</currency> </purchaseTotals> <apAuthReply> <reasonCode>100</reasonCode> <status>AUTHORIZED</status> <processorResponse>00003</processorResponse> <amount>75.00</amount> <dateTime>2023-10-06T19:33:21Z</dateTime> <paymentStatus>authorized</paymentStatus> <responseCode>00003</responseCode> <reconciliationID>XFZ55NET9PYQ</reconciliationID> <processorTransactionID>519ff272-d850-4c81-ab65-674f670063c7</processorTransactionID> </apAuthReply> </>
Request with Optional Line Items
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748
<="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantID>test_merchant</merchantID> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <billTo> <firstName>John</firstName> <lastName>Smith</lastName> <street1>Peachtree St</street1> <city>Atlanta</city> <state>GA</state> <postalCode>33019</postalCode> <country>US</country> <email>test@cybs.com</email> </billTo> <shipTo> <firstName>John</firstName> <lastName>Smith</lastName> <street1>Peachtree St</street1> <city>Atlanta</city> <state>GA</state> <postalCode>33019</postalCode> <country>US</country> </shipTo> <item id="0"> <unitPrice>1</unitPrice> <quantity>10</quantity> <productCode>4564</productCode> <productName>TV</productName> <productSKU>testI</productSKU> <totalAmount>10</totalAmount> </item> <item id="1"> <unitPrice>15</unitPrice> <quantity>1</quantity> <productCode>65432</productCode> <productName>TV</productName> <productSKU>testJ</productSKU> <totalAmount>15</totalAmount> </item> <purchaseTotals> <currency>USD</currency> </purchaseTotals> <apPaymentType>AFP</apPaymentType> <apAuthService run="true"> <cancelURL>https://www.test.com</cancelURL> <successURL>https://www.test1.com</successURL> <preapprovalToken>0d97aa1b-a9dd-4e9c-b60c-b1157470d034</preapprovalToken> </apAuthService> </>
Response with Optional Line Items
123456789101112131415161718192021
<:c="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <requestID>6977375233876065503009</requestID> <decision>ACCEPT</decision> <reasonCode>100</reasonCode> <requestToken>AxjnrwSTej6Ib33u98chAAUZYiy69adJpUaUiInkFtpV8ukDJxDNyGTSTL0YwW2Lkm9H0Q3vvd745CAA6Qe8</requestToken> <purchaseTotals> <currency>USD</currency> </purchaseTotals> <apAuthReply> <reasonCode>100</reasonCode> <status>AUTHORIZED</status> <processorResponse>00003</processorResponse> <amount>25.00</amount> <dateTime>2023-10-19T17:45:24Z</dateTime> <paymentStatus>authorized</paymentStatus> <responseCode>00003</responseCode> <reconciliationID>XEKWVNIRQRHD</reconciliationID> <processorTransactionID>0d97aa1b-a9dd-4e9c-b60c-b1157470d034</processorTransactionID> </apAuthReply> </>
Light Dark
Request
123456789101112
<="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantID>test_merchant</merchantID> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <purchaseTotals> <currency>USD</currency> <grandTotalAmount>1</grandTotalAmount> </purchaseTotals> <apPaymentType>afp</apPaymentType> <apCaptureService run="true"> <authRequestID>6246274241256683803069</authRequestID> </apCaptureService> </>
Response to a Successful Request
123456789101112131415161718
<:c="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <requestID>6246277717236180203285</requestID> <decision>ACCEPT</decision> <reasonCode>100</reasonCode> <purchaseTotals> <currency>USD</currency> </purchaseTotals> <apCaptureReply> <reasonCode>100</reasonCode> <status>SETTLED</status> <processorResponse>00004</processorResponse> <amount>1.00</amount> <reconciliationID>XFZOSQ97H6UE</reconciliationID> <paymentStatus>settled</paymentStatus> <responseCode>00004</responseCode> </apCaptureReply> </>
Light Dark
Request
1234567891011121314151617181920212223242526272829303132333435
<="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantID>test_merchant</merchantID> <merchantReferenceCode>ref-1234</merchantReferenceCode> <billTo> <firstName>John</firstName> <lastName>Smith</lastName> <street1>Happy St</street1> <city>Austin</city> <state>TX</state> <postalCode>78757</postalCode> <country>US</country> <email>test@cybs.com</email> </billTo> <shipTo> <firstName>John</firstName> <lastName>Smith</lastName> <street1>Happy</street1> <city>Austin</city> <state>TX</state> <postalCode>78757</postalCode> <country>US</country> <phoneNumber>33623456789</phoneNumber> </shipTo> <purchaseTotals> <currency>USD</currency> <grandTotalAmount>100.00</grandTotalAmount> </purchaseTotals> <apPaymentType>afp</apPaymentType> <apSaleService run="true"> <cancelURL>http://test0.com</cancelURL> <successURL>http://test1.com</successURL> <failureURL>http://test2.com</failureURL> <preapprovalToken>c25e5752-ce21-4426-9b77-635a2d6a7aee</preapprovalToken> </apSaleService> </>
Response to a Successful Request
12345678910111213141516171819
<:c="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <requestID>6246055293446455103056</requestID> <decision>ACCEPT</decision> <reasonCode>100</reasonCode> <purchaseTotals> <currency>USD</currency> </purchaseTotals> <apSaleReply> <reasonCode>100</reasonCode> <paymentStatus>pending</paymentStatus> <responseCode>00001</responseCode> <merchantURL>https://portal.afterpay.com/us/checkout/?token=002.co8</merchantURL> <processorTransactionID>ab19e56a-1056</processorTransactionID> <reconciliationID>XFZOQQ97FEIW</reconciliationID> <amount>10.00</amount> <processorResponse>00001</processorResponse> </apSaleReply> </>
Light Dark
Request
123456789101112
<="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantID>test_merchant</merchantID> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <purchaseTotals> <currency>USD</currency> <grandTotalAmount>1</grandTotalAmount> </purchaseTotals> <apPaymentType>afp</apPaymentType> <apRefundService run="true"> <refundRequestID>6246277717236180203285</refundRequestID> </apRefundService> </>
Response to a Successful Request
1234567891011121314151617181920
<:c="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <requestID>6246279076626811503016</requestID> <decision>ACCEPT</decision> <reasonCode>100</reasonCode> <purchaseTotals> <currency>USD</currency> </purchaseTotals> <apRefundReply> <reasonCode>100</reasonCode> <transactionID>47797f6a-d894-428b-91d2-8408e8a53c5a</transactionID> <status>REFUNDED</status> <processorResponse>00006</processorResponse> <amount>1.00</amount> <reconciliationID>XFZOSQ97H6UE</reconciliationID> <returnRef>EE3FLQ9GXCWH</returnRef> <paymentStatus>refunded</paymentStatus> <responseCode>00006</responseCode> </apRefundReply> </>
Light Dark
Request
12345678
<="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantID>test_merchant</merchantID> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <apPaymentType>afp</apPaymentType> <apAuthReversalService run="true"> <authRequestID>6246274241256683803069</authRequestID> </apAuthReversalService> </>
Response to a Successful Request
123456789101112131415
<:c="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <requestID>6246062044236748603086</requestID> <decision>ACCEPT</decision> <reasonCode>100</reasonCode> <apAuthReversalReply> <reasonCode>100</reasonCode> <status>AUTH_REVERSED</status> <processorResponse>00007</processorResponse> <amount>10.00</amount> <paymentStatus>auth_reversed</paymentStatus> <responseCode>00007</responseCode> <reconciliationID>XFZONQ96WTF2</reconciliationID> </apAuthReversalReply> </>
Light Dark
Request
12345678
<="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantID>test_merchant</merchantID> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <apPaymentType>afp</apPaymentType> <apCheckStatusService run="true"> <checkStatusRequestID>6246036783396181003073</checkStatusRequestID> </apCheckStatusService> </>
Response to a Successful Request
123456789101112
<:c="urn:schemas-cybersource-com:transaction-data-1.213"> <merchantReferenceCode>refnum-1234</merchantReferenceCode> <requestID>6246049907006336203063</requestID> <decision>ACCEPT</decision> <reasonCode>100</reasonCode> <apCheckStatusReply> <reasonCode>100</reasonCode> <reconciliationID>XFZOPQ97EIXG</reconciliationID> <paymentStatus>pending</paymentStatus> <processorResponse>00001</processorResponse> </apCheckStatusReply> </>