AMEX
American Express (AMEX) is a premier global payment network known for high-value cardholders and advanced security protocols. By integrating directly with AMEX via ISO 8583, Deuna merchants bypass third-party gateways to reduce latency, minimize processing costs, and gain granular control over transaction data.
As a payment and fraud orchestrator, our platform allows you to easily connect your AMEX merchant account directly into your payment flow. This enables you to leverage AMEX’s processing capabilities as part of a sophisticated, rules-based payment strategy, helping you optimize acceptance rates and reduce costs.
This guide will walk you through the credentials needed to connect AMEX in our Admin.
Requisites
Before you can configure AMEX in our Admin, you must have an active merchant account with them. During your onboarding, AMEX will provide you with a set of unique credentials for your direct ISO integration.
Please gather the following required fields from your AMEX integration manager or welcome documents:
- Affiliation ID (Merchant ID, SE Number): Your unique 10-digit identifier for your merchant account.
- Terminal ID: a unique code that identifies a specific terminal at a Merchant location.
Configuration Steps
Connecting AMEX is a simple, one-time setup in our Admin portal.
-
Log in to your Admin portal.
-
Navigate to Connections under Payments section**,** find AMEX and select Connect.
-
A form will appear. Carefully enter the following information along with the credentials gathered from AMEX and your Deuna advisor
Name Detail Currency Select the Payment processor currency Affiliation ID Your unique 10-digit identifier for your merchant account obtained from AMEX Submitter ID (Provided by Deuna) Submitter ID provided by your Deuna advisor Acquirer Afiliation ID Use “100000000” unless AMEX or Deuna advices a different value. Terminal ID (Suggested "00000001") Use “00000001” unless AMEX or Deuna advices a different value. Point of sale (POS) data code (Default "1000S0100010") Use “1000S0100010” unless AMEX or Deuna advices a different value. Merchant Category Code (4 digit) Your 4-digit category code as “4511” Approval code length (Default "6") Use “6” unless AMEX or Deuna advices a different value. Merchant Name Merchant commercial name Merchant Address (street, number, interior number) The merchant Address composed by street, number, and interior (if applies). Merchant City The city where the merchant is registered Merchant Postal Code (e.g. "11510") The Postal Code where the services are provided or the merchant is registered Merchant State Code (3 digits) The 3-digit State Code where the services are provided or the merchant is registered Merchant Country code (numeric 3 digits) The country where the services are provided or the merchant is registered, in 3 numeric digit format. Seller ID (Only for aggregator mode. Default "0000000000") Use “0000000000” unless AMEX or Deuna advices a different value. Seller email (Only for aggregator mode. Default "[email protected]") Use “[email protected]” unless AMEX or Deuna advices a different value. Seller phone (Only for aggregator mode. Default "55555555555") Use “55555555555” unless AMEX or Deuna advices a different value. Message reason code (Default "1900") Use “1900” unless AMEX or Deuna advices a different value. Auth Processing Code ("004000" or "004800" to enable AAV) In case you decide to use AMEX’s Address Verification service (AVV) use “004800”, otherwise, use “004000”. Automated Address Verification (AAV) Type ("AD" or "AE". Suggested "AD") If you decided to use AMEX’s AAV: Use "AD" (suggested) or "AD" depending on your requirtements:
- Authorization, Standard (AD): it is used to submit various levels of Cardmember and shipping data for verification.Authorization, - Enhanced (AE): supports all of the functionality of the AD format while providing additional verification options for Cardmember Billing Phone Number and Customer Email.
In case you won’t use AMEX’s AAV, use “AD” in this field. |
-
Select if you want this connection in a Sale (Purchase) or Pre Authorization (Authorization) mode.
-
If required, you can enable our 3DS MPI to secure transactions with AMEX following this guide.
-
Click "Save".
-
Our system will validate the credentials, and AMEX will appear as "Active" in your list of connected processors.
Technical Details: ISO 8583 Authorization
Our integration utilizes the 1100 (Authorization Request) and 1110 (Authorization Response) message types. To maintain high approval rates and ensure liability shift, the following fields are mandatory or highly recommended:
Note: This is a representative list of the most common fields used for an e-commerce authorization and not an exhaustive specification
| Field | Field Name | Description |
|---|---|---|
| MTI | Message Type Identifier | 1100 Indicates an Authorization Request |
| Field 2 | Primary Account Number (PAN) | The customer's 16-19 digit card number. Shown masked as a Card ID number. |
| Field 3 | Processing Code | Indicates the transaction type (e.g., 200000 for Purchase). |
| Field 4 | Amount, Transaction | The total purchase amount in the transaction currency. Shown in cents. |
| Field 7 | Transmission Date and Time | The date and time the transaction was initiated (MMDDhh:mm:ss). |
| Field 11 | System Trace Audit Number (STAN) | A unique 6-digit number to identify the transaction. |
| Field 12 | Transaction local date and time | The date and time the transaction was initiated (YYMMDDhh:mm:ss). |
| Field 14 | Expiration Date | The card's expiration date in YYMM format. Shown hashed. |
| Field 19 | Country Code | 3-digit country code of the transaction. Shown hashed. |
| Field 22 | POS Data | For e-commerce, this indicates card-not-present status. Expect “1000S0100010” |
| Field 24 | Function code | Operation 3-digit code (authorization, refund, etc). Shown hashed. |
| Field 25 | Message reason code | Message reason code (”1900”). Shown hashed. |
| Field 26 | Card acceptor business code | Merchant’s MCC. |
| Field 27 | Approval code | Approval code length ("6") |
| Field 32 | Acquirer Institution ID | Acquirer Afiliation ID. Example “100000000”. |
| Fiel 37 | Retrieval Reference Number | 12-digit unique value over 24 hour period to identify the transaction. Shown hashed. |
| Field 41 | Card Acceptor Terminal ID | Your 8-digit Terminal ID (TID). Example “00000001” |
| Field 42 | Card acceptor identification code (Merchant ID) | Your 10-digit Merchant ID (from your settings). |
| Field 43 | Card acceptor name location | Merchant Name, Merchant City Name as defined in the credentials |
| Field 47 | Additional data national | Billing, Shipping, and Airline details |
| Field 48 | Additional private data | American Express Extended Payment Indicator, which consists of the Plan Type and the Number of Installments. Plan types are 03 (installment plan), and 05 (deferred months): Example: “0306”. Can be shown hashed. |
| Field 49 | Currency Code, Transaction | The 3-digit numeric ISO currency code (e.g., 840 for USD). Shown hashed |
| Field 61 | National Use Data | Contains 3-D Secure 2.x and merchant details |
| Field 63 | Private Data | Contains AAV Data |
Field 47 Additional Data National (Billing, Shipping, and Airline details)
| Field 47 | Field Name | Description |
|---|---|---|
| Subfield 0 | Brand and Transaction type | Concat of two digit card brand code, **in case is not airlines or IAC if is airline order. “**AXITD” |
| Subfield 1 | (Not sent in Airline orders) CUSTOMER EMAIL ID (CE ID) | Customer Email ID is constant literal “CE” |
| Subfield 2 | (Not sent in Airline orders) CUSTOMER EMAIL | Example: [email protected] |
| Subfield 3 | (Not sent in Airline orders) CUSTOMER HOSTNAME ID (CHID) | Customer HostName ID is constant literal “CH ” |
| Subfield 4 | (Not sent in Airline orders) CUSTOMER HOSTNAME. | The customer’s email domain. Example “GMAIL.COM” |
| Subfield 5 | (Not sent in Airline orders) HTTP BROWSER TYPE ID (HBT ID) | HTTP Browser Type ID is constant literal “HBT” |
| Subfield 6 | (Not sent in Airline orders) HTTP BROWSER TYPE | User agent from the request: Example: MOZILLA/4.0~(COMPATIBLE; |
| Subfield 7 | (Not sent in Airline orders) SHIP TO COUNTRY ID (STC ID) | Ship To Country ID is constant literal “STC” |
| Subfield 8 | (Not sent in Airline orders) SHIP TO COUNTRY | Three-digit numeric Country Code. Example 840 |
| Subfield 9 | (Not sent in Airline orders) SHIPPING METHOD ID (SM ID) | Shipping Method ID is constant literal “SM" |
| Subfield 10 | (Not sent in Airline orders) SHIPPING METHOD | Value for pickup orders is “06”, otherwise “03” (shipping_options.type) |
| Subfield 11 | (Not sent in Airline orders) MERCHANT PRODUCT SKU ID (MPS ID) | Merchant Product SKU ID is constant literal“MPS” |
| Subfield 12 | (Not sent in Airline orders) MERCHANT PRODUCT SKU | SKU of the most expensive item sent in the order. In case no SKU is sent, the value is "ND" |
| Subfield 13 | (Not sent in Airline orders) CUSTOMER IP | Customer's Internet IP address |
| Subfield 14 | (Not sent in Airline orders) CUSTOMER ANI | phone without “+” or spaces |
| Subfield 16 | (Only for Airline orders) DEPARTURE DATE | Departure Date (format CCYYMMDD) as “20030101” |
| Subfield 17 | (Only for Airline orders) AIRLINE PASSENGER NAME ID (APN ID) | Airline Passenger Name ID is constant literal“APN” |
| Subfield 18 | (Only for Airline orders) PASSENGER NAME | Passenger Name in format: "FROST JANE M MRS" |
| Subfield 19 | (Only for Airline orders) ORIGIN (Origin Airport) | Origin Airport for first travel segment of trip: IATA code of the origin airport as “SEA” |
| Subfield 20 | (Only for Airline orders) DEST | Destination Airport for first travel segment of trip: IATA code of the destination airport JFK |
| Subfield 21 | (Only for Airline orders) ROUTING ID (RTG ID) | Routing ID is constant literal “RTG” |
| Subfield 22 | (Only for Airline orders) NUMBER OF CITIES | Count of total cities visities from both origin and destination airports. |
| Subfield 23 | (Only for Airline orders) ROUTING CITIES | Routing Airport or City Codes for each leg onticket (including ORIGIN and DEST): STL / JFK / MIA |
| Subfield 24 | (Only for Airline orders) AIRLINE CARRIERS ID (ALC ID) | Airline Carriers ID is constant literal “ALC” |
| Subfield 25 | (Only for Airline orders) NUMBER OF AIRLINE CARRIERS | Number of Airline Carriers on the trip |
| Subfield 26 | (Only for Airline orders) AIRLINE CARRIERS | Airline Carrier Code for each leg on ticket (including ORIGIN and DEST). Example AB / DC / EF |
| Subfield 27 | (Only for Airline orders) FARE BASIS | “Business” |
| Subfield 28 | (Only for Airline orders) NUMBER OF PASSENGERS | Number of passengers in the format: 001 |
| Subfield 29 | (Only for Airline orders) USTOMER IP | Customer's Internet IP address. Example 127.142.151.223 |
| Subfield 30 | (Only for Airline orders) USTOMER EMAIL ID (CE ID) | Customer Email ID is constant literal “CE” |
| Subfield 31 | (Only for Airline orders) USTOMER EMAIL ID | Customer's email address. Example:[email protected] |
Field 61 Key subfields (3DS details)
| Field 61 | Field Name | Description |
|---|---|---|
| Subfield 0 | Primary and Secondary ID | Constant value “AXASK” |
| Subfield 1 | ELECTRONIC COMMERCE INDICATOR (ECI) | Possivle values: 05 = Authenticated with AEVV, 06 = Attempted with AEVV, 07 = Not Authenticated |
| Subfield 2 | AMERICAN EXPRESS VERIFICATION VALUE (AEVV) ID | Constant value “AEVV” |
| Subfield 3 | AMERICAN EXPRESS VERIFICATION VALUE | (AEVV) cryptographic value derived by the Issuer with the results American ExpressSafeKey payment authentication results. It is a 28-chars base64, when decoded can show key information about the performed analysis. Example: “AAkBAmRGkyNEM1J5EkaTAAAAAAA=" |
| Subfield 4 | AMERICAN EXPRESS SAFEKEY TRANSACTION ID (XID) | Constant value “XID” |
| Subfield 5 | AMERICAN EXPRESS SAFEKEY TRANSACTION ID VALUE | American Express SafeKey Transaction Identifier is determined during the American Express SafeKey payment authentication. Base64 value. Example: “AgIAADm0+B7htUfXuLAUcDlOUtM=” |
Field 63 Key subfields (AAV data)
| Field 63 | Field Name | Description |
|---|---|---|
| Subfield 1 | SERVICE IDENTIFIER (AX) | Constant “AX” |
| Subfield 2 | REQUEST TYPE IDENTIFIER | AAV Type selected in the configuration, either “AD” or “AE” |
| Subfield 3 | CARDMEMBER BILLING POSTAL CODE | Example “98107” |
| Subfield 4 | CARDMEMBER BILLING ADDRESS | Example “6201 14TH AVE NW” |
| Subfield 5 | CARDMEMBER FIRST NAME | Example “LEAO” |
| Subfield 6 | CARDMEMBER LAST NAME | Example “BUTRON” |
| Subfield 7 | CARDMEMBER BILLING PHONE NUMBER | Billing phone number. Example “4155688537” |
| Subfield 8 | SHIP-TO POSTAL CODE | Example “98107” |
| Subfield 9 | SHIP-TO ADDRESS | Example “6201 14TH AVE NW” |
| Subfield 10 | SHIP-TO FIRST NAME | Example “LOURDES” |
| Subfield 11 | SHIP-TO LAST NAME | Example “MONTENEGRO” |
| Subfield 12 | SHIP-TO PHONE NUMBER | Example “4155797662” |
| Subfield 13 | SHIP-TO COUNTRY CODE | Country code in 3-digit number as “840” |
Both Request and Responses share the same field names and information in most cases, being the main difference in the field 38 and 39, which are related to the authorization results:
- Field 38: Authorization code authorization or reversal (void) request.
- Field 39: Approved Authorization requests will have the value “000”, and Approved Reversals request will have the value“400” in case of reversals (void). Every different value will be related to an error code that will be displayed in the Admin along with its description.
- Field 44: AVS result code expressed in one-digit letter. The possible values are explained in the next section.
AVS Results
When AMEX AVS (AAV) is enabled in the configuration with the value “004800”, the field 44 will return the AVS result in one-digit letters, that will have an equivalent in Deuna AVS error codes:
| Amex AAV code | Definition | Deuna AVS code |
|---|---|---|
| Z | Only ZIP code is correct | A01 |
| A | Only Address is correct | A02 |
| K | Only Cardholder Name is correct | A03 |
| O | Cardholder Name and Address are correct | A04 |
| L | Cardholder Name and ZIP code are correct | A05 |
| Y | Address and ZIP code are correct | A06 |
| N | Address and ZIP code are incorrect | A07 |
| M | Cardholder Name, Address, and ZIP are correct | A08 |
| E | Cardholder Name incorrect, Address correct, ZIP code correct | A12 |
| F | Cardholder Name incorrect, Address correct, ZIP code incorrect | A13 |
| D | Cardholder Name incorrect, Address incorrect, ZIP code correct | A14 |
| W | Cardholder Name, Address, and ZIP code are all incorrect | A15 |
| U | Address verification information is not available | A16 |
| S | Address verification is not allowed | A17 |
| R | Address verification is not available, Retry. | A18 |
Next Steps
Your AMEX connection is now active!
The final step is to incorporate it into your transaction flow. Go to the Payment Strategy section of the Admin to build rules that define which transactions are routed to AMEX (e.g., "Route all transactions in EUR to AMEX").
Updated 1 day ago