Payer Authentication Reports
This section describes the Payer Authentication reports that you can download from the .
All reports on the production servers are retained for 16 months, but the transaction history is kept in the database for only 12 months. All reports on the test servers are deleted after 60 days. Only processed transactions appear in reports. Transactions that result in a system error or a time-out are not included.
To get access to the reports, you must file a support ticket in the Support Center.
Payer Authentication Summary Report
This daily, weekly, and monthly summary report indicates the performance of the enrollment and validation services as a number of transactions and a total amount for authentication screens your transactions: successful, attempted, and incomplete authentication. The cards reported are Visa, Mastercard, China UnionPay, Elo, and American Express. This daily report is generally available by 7:00 a.m. ET. Data in this report remains available for 6 months.
Download the Report
Follow these steps to view the Payer Authentication Summary report:
- In the left navigation panel, click the Reports icon.
- Under Transaction Reports, click Payer Auth Summary. The Payer Auth Summary Report page appears.
- In the search toolbar, select a date range to include in the report. Account-level users must select a merchant as well.
- Based on the date range you selected, choose the specific day, week, or month you want to review.
Only months that have already occurred in the current year display in the Month list. To view all months of a previous year, select the year first, and then choose the month. To view results from before the selected period, click Previous. Click Next to see the next period.
Interpreting the Report
The report is organized by card type. In each card type section, currencies are reported alphabetically. For each currency, a summary of your payer authentication validation results appears as a total amount and number of transactions.
| Card Type | Protected? | Commerce Indicator | ECI |
|---|---|---|---|
| Visa, American Express | No (no authentication) | Internet | 7 |
| Visa, American Express | Yes (recorded attempt) | VbV, Desk, or JS Attempted | 6 |
| Visa, American Express | Yes (successful) | VbV, JS, or Aesk | 5 |
| Mastercard, Meeza, Maestro | No (no authentication) | Internet | 7 |
| Mastercard, Meeza, Maestro | Yes (recorded attempt) | SPA | 1 |
| Mastercard, Meeza, Maestro | Yes (successful) | SPA | 2 |
Comparing Payer Authentication and Payment Reports
The Payer Authentication report and the payment reports might differ when an authenticated transaction is not authorized.
The values (amounts and counts) in the Payer Authentication report might not match your other sources of reconciliation. This report shows the transactions validated by payer authentication. A different number of transactions might have been authorized.
The amounts and numbers can be higher in the Payer Authentication report than in the payment reports. To reconcile your reports more easily when using payer authentication, attempt to authenticate the same amount that you want to authorize.
Example: For 10,000 orders, you might receive these results:
- 9,900 successful enrollment checks (Payer Authentication report)
- 9,800 successful authentication checks (Payer Authentication report)
- 9,500 successful authorization checks (Payment report)
Payer Authentication Detail Report
This section describes the elements of the Payer Authentication Detail report.
Report Element
The Report element is the root element of the report.
<Report><PayerAuthDetails> (PayerAuthDetail+)</PayerAuthDetails></Report>Child Elements of Report:
| Element Name | Description |
|---|---|
PayerAuthDetails | Contains the transactions in the report. |
PayerAuthDetail Element
Each PayerAuthDetail element represents one transaction.
<PayerAuthDetail> (RequestID) (MerchantID) (RequestDate) (TransactionType) (PAReq)? (PARes)? (AuthInfo)?</PayerAuthDetail>Child Elements of PayerAuthDetail:
| Element Name | Description | Type and Length |
|---|---|---|
RequestID | Unique identifier generated for the transaction. Corresponds to the request ID. | Numeric (26) |
MerchantID | Merchant ID used for the transaction. | String (30) |
RequestDate | Date on which the transaction was processed. | DateTime (25) |
TransactionType | One of: ics_auth (Card authorization service), ics_pa_enroll (Payer Authentication Enrollment Check), ics_pa_validate (Payer Authentication Validation). | String (20) |
| PAReq | The Payer Authentication Request message sent to the ACS. | — |
| PARes | The Payer Authentication Response message sent by the ACS. | — |
AuthInfo | Authorization information. | — |
PAReq Element
The PAReq element contains the payer authentication request message. This element corresponds to the payerAuthEnrollReply_paReq API field.
<PAReq> (AcqBIN) (MerID) (Name) (Country) (URL) (XID) (Date) (PurchaseAmount) (AcctID) (Expiry)</PAReq>Child Elements of PAReq:
| Element Name | Description | Type and Length |
|---|---|---|
AcqBIN | First six digits of the acquiring bank's identification number. | Numeric (6) |
MerID | Identifier provided by your acquirer to the merchant to log in to the ACS URL. | String (24) |
Name | Merchant's company name. | String (25) |
Country | Two-character code for the merchant's country of operation. | String (2) |
URL | Merchant's business website. | String |
XID | Unique transaction identifier. | — |
Date | Date and time of the request. | DateTime (25) |
PurchaseAmount | Authorization amount and currency for the transaction. | — |
AcctID | Customer's account information (Base64-encoded PAN). | — |
Expiry | Card expiration date. | — |
PARes Element
The PARes element contains the payer authentication response.
<PARes> (AcqBIN) (MerID) (XID) (Date) (PurchaseAmount) (PAN) (AuthDate) (Status) (CAVV) (ECI)</PARes>Child Elements of PARes:
| Element Name | Description | Type and Length |
|---|---|---|
AcqBIN | First six digits of the acquiring bank's identification number. | Numeric (6) |
MerID | Identifier provided by your acquirer; used to log in to the ACS URL. | String (24) |
XID | XID value returned in the customer authentication response. Corresponds to the payerAuthValidateReply_xid API field. | String (28) |
Date | Date and time of the request. | DateTime (25) |
PurchaseAmount | Authorization amount and currency for the transaction. | — |
PAN | Customer's masked Primary Account Number. | — |
AuthDate | Date and time of the authentication. | — |
Status | Authentication status. | — |
| CAVV | Cardholder Authentication Verification Value. | — |
| ECI | Electronic Commerce Indicator. | — |
AuthInfo Element
<AuthInfo> (AVSResult) (CVVResult)</AuthInfo>Child Elements of AuthInfo:
| Element Name | Description | Type and Length |
|---|---|---|
AVSResult | Results of the address verification test. | String (1) |
CVVResult | Results of the card verification number test. | String (1) |
Report Examples
These examples show a complete transaction: the failed enrollment check (enrolled card) and the subsequent successful authentication.
Failed Enrollment Check:
<?xml version="1.0" encoding="utf-8"?><!DOCTYPE Result SYSTEM "/reporting/v3/dtd/padr"><Report Name="Payer Authentication Detail" Version="1.0" xmlns="/reporting/v3/dtds/padr" MerchantID="sample_merchant_id" ReportStartDate="2022-02-09T08:00:00-08:00" ReportEndDate="2022-02-10T08:00:00-08:00"><PayerAuthDetails> <PayerAuthDetail RequestID="1895549430000167904548" TransactionType="ics_pa_enroll" RequestDate="2022-02-09T08:00:02-08:00"> <ProofXML> <Date>20220209 08:00:34</Date> <DSURL>https:123.456.789.01:234/DSMsgServlet</DSURL> <PAN>XXXXXXXXXXXX0771</PAN> <AcqBIN>123456</AcqBIN> <MerID>4444444</MerID> <Password /> <Enrolled>Y</Enrolled> </ProofXML> <VEReq> <PAN>XXXXXXXXXXXX0771</PAN> <AcqBIN>123456</AcqBIN> <MerID>example</MerID> </VEReq> <VERes> <Enrolled>Y</Enrolled> <AcctID>NDAxMjAwMTAxMTAwMDc3MQ==</AcctID> <URL>https://www.sample_url.com</URL> </VERes> </PayerAuthDetail></PayerAuthDetails></Report>Thanks for your feedback!
Last published: September 29, 2026