SOAP API EMV Appendix
The purpose of this guide is to provide an overview for card present implementation through SOAP API.
EMV Request (using TLVData)
The following XML document represents an example of a Card Present transaction using the minimal set of elements:
<ipgapi:IPGApiOrderRequest
xmlns:v1="http://ipg-online.com/ipgapi/schemas/v1"
xmlns:ipgapi="http://ipg-online.com/ipgapi/schemas/ipgapi">
<v1:Transaction>
<v1:CreditCardTxType>
<v1:Type>sale</v1:Type>
</v1:CreditCardTxType>
<v1:EMVCardPresentRequest>
<v1:CryptData>
<v1:SRED>
<v1:Value>59E54F4798AFC82C09C93EA1D2757E8F7B9A4C5082F76041</v1:Value>
<v1:KSN>9A2133026261C0600001</v1:KSN>
</v1:SRED>
<v1:PINBlock>
<v1:Value>68XXXXXXXXXXXX26</v1:Value>
<v1:KSN>9A214A00000040800005</v1:KSN>
</v1:PINBlock>
</v1:CryptData>
<v1:TLVData>950500000000009F390107500B56495341204352454449545F2002202F5F2A0209785F340101820220008407A00000000310109A031604229C01009F02060000000009009F03060000000000009F0607A00000000310109F090200019F100706010A03A000009F1A0203009F1C0831323334353637389F1E0831303030303439369F26082891CDC96B987F0E9F2701809F3303E0F8C89F3501229F3602034E9F37048D8B26AD9F4104000000389F660426804000DF280100DF30020301DFAE021859E54F4798AFC82C09C93EA1D2757E8F7B9A4C5082F76041DFAE030A9A2133026261C0600001DFAE5711476173FFFFFF0010D22122011143844489
</v1:TLVData>
</v1:EMVCardPresentRequest>
<v1:Payment>
<v1:ChargeTotal>9</v1:ChargeTotal>
<v1:Currency>978</v1:Currency>
</v1:Payment>
<TransactionDetails>
<OfflineApprovalType>OFFLINE_APPROVAL</OfflineApprovalType>
<ReferenceNumber>13458</ReferenceNumber>
</TransactionDetails>
</v1:Transaction>
</ipgapi:IPGApiOrderRequest>
CryptData
In order to send card data and Online PIN data in a secure way to the Gateway, DUKPT key management is used with separated BDK’s (Base derivation Keys) for card data encryption (SRED) and PIN. The KSN format is defined as follows:
• SRED: the encrypted card information is expected
• PINBlock: optional, only used for online PIN
• MAC: conditional, only used if agreed with Gateway implementation team upfront
Key Serial Number (KSN) should be always provided along with the cryptogram.
KSN in Gateway's HSMD to identify a certain BDK consists of:
| Field | Number of bits | Description |
|---|---|---|
| BDK Identifier 24 | 24 | Identifies the BDK to be used for security operations as counterpart for the DUKPT session keys. |
| Terminal Serial | 24 | The serial number for the terminal, either assigned OR the physical number. |
| Load counter | 11 | The number of remote key injections that already took place |
| Transaction counter | 21 | The actual number of transactions increased per transaction. |
Note
• BDK Identifier must have a length of 24 Bits – so the BDK is only selected on the Gateway by this unique identifier
• Terminal Serial Field identifies a specific terminal
• Load counter is used to allow a reset of the transaction counter to 0, when a new key injection is done.
• Transaction counter: must be increased for a specific device for each TX. Can be reset to 0 after a new key injection, when the load counter was incremented.
• If dealing with German local scheme (girocard), it is important, that the combination of load counter and transaction counter is always growing.
SRED
The SRED field must be filled with the following data depending on TX technology used. The data described below will be concatenated and then padded with 0x00 to have a length dividable by 8 (needed for 3DES DUKPT encrypting).
The data will be prefixed by a 5 digit ASCII value to inform the decrypting device what kind of SRED data is passed and to check if decryption was successful:
Magnetic stripe TX / MSD contactless TX
“SECMS” + DF8046 + padding with 0x00
EMV contact TX
“SECIC” + 57 + 5A(o) + padding with 0x00
EMV contactless TX
“SECRF” + 57 + 5A(o) + padding with 0x00
Manual entered data
“SECMA” + DF8003 + DF8004 + DF8005(o) + padding with 0x00
| Tag | Name | Format | Length | Set | Description |
|---|---|---|---|---|---|
| 57 | EMV Track2 data | binary | var | 1 | EMV tag 57 (track 2 equivalent data) as received from the used chip card |
| 5A | EMV PAN data | binary | var | 1 | EMV tag 5A (primary account number) as received from the used chip card |
| DF8046 | Track 2 data | alphanumeric | var | 1 | Plain text track 2 data excluding start and end sentinel (defined for internal use – will not be used externally) |
| DF8003 | Manual PAN | alphanumeric | var up to 19 | 1 | Manually entered PAN to be encrypted by terminal |
| DF8004 | Manual expiry date | alphanumeric | 4 | 1 | Manually entered expiry date in format YYMM to be encrypted by terminal |
| DF8005 | Manual CVC | alphanumeric | var up to 4 | 1 | Manually entered CVC to be encrypted by terminal |
| DF807F | Autovoid Indicator | AutoVoid Indicator (1= AutoVoid or technical Void.) This is sent by the terminal to differentiate between manual void and automatic void. In some endpoint protocols (e.g HPDH) an AutoVoid will result in sending a different MTI to the endpoint. |
Example for Manual data – 40 Bytes:
0x53 0x45 0x43 0x4D 0x41 (Header – 5)
0xDF 0x80 0x03 0x10 0x35 0x32 0x36 0x36 0x31 0x32 0x33 0x34 0x31 0x32 0x33 0x34
0x31 0x32 0x33 0x34 (Manual keyed PAN – 20)
0xDF 0x80 0x04 0x04 0x31 0x32 0x31 0x33 (Manual keyed expiry – 8)
0x00 0x00 0x00 0x00 0x00 0x00 0x00 (Padding – 7)
Example for EMV contactless TX (SECRF):
00000000 53 45 43 52 46 57 13 12 34 56 78 90 12 34 56 d2 |SECRFW.T........|
00000010 21 22 01 11 48 35 94 90 00 0f 5a 08 54 13 33 00 |................|
00000020 89 09 91 30 00 00 00 00 |........|
| Position | Content | Description |
|---|---|---|
| 0 – 4 | 0x53, 0x45, 0x43, 0x52, 0x46 | The ASCII encoded string “SECRW” |
| 5 - 25 | 0x57, 0x13, 0x12, 0x34, 0x56, 0x78, 0x90, 0x12, 0x34, 0x56, 0xd2, 0x21, 0x22, 0x01, 0x11, 0x48, 0x35, 0x94, 0x90, 0x00, 0x0f | The complete tag 57 (track-2) including tag and length field. The last ‘f’ is a filler, because in this example the track-2 data consists of an odd number of characters. The ‘=’ delimiter is translated into a 0xd |
| 26 - 35 | 0x5a, 0x08, 0x12, 0x34, 0x56, 0x78, 0x90, 0x12, 0x34, 0x56 | |
| 36 – 39 | 0x00, 0x00, 0x00, 0x00 | Padding bytes to have a total length which is a multiple of 8 |
Example for Magnetic stripe TX / MSD contactless TX (SECMS):
00000000 53 45 43 4d 53 df 80 46 24 31 32 33 34 35 36 37 |SECMS..F$1234567|
00000010 38 39 30 31 32 33 34 35 36 3d 32 32 31 32 32 30 |890123456=221220|
00000020 31 31 32 33 34 30 30 30 30 36 37 38 30 00 00 00 |1123400006780...|
| Position | Content | Description |
|---|---|---|
| 0 – 4 | 0x53, 0x45, 0x43, 0x4d, 0x53 | The ASCII encoded string “SECMS” |
| 5 - 44 | 0xdf, 0x80, 0x46, 0x24, 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, 0x37, 0x38, 0x39, 0x30, 0x31, 0x32, 0x33, 0x34, 0x35, 0x36, 0x3d, 0x32, 0x32, 0x31, 0x32, 0x32, 0x30, 0x31, 0x31, 0x32, 0x33, 0x34, 0x30x 0x30, 0x30, 0x30, 0x36, 0x37, 0x38, 0x30 | The complete tag DF8046 (track-2) including tag and length field. In this case the value part of the tag is ASCII encoded. |
| 45 – 47 | 0x00, 0x00, 0x00 | Padding bytes to have a total length which is a multiple of 8 |
PIN Block
Optional, only used for online PIN transactions – currently ISO-0 and ISO-1 PIN blocks are supported. The PINBlock is also contained in the CryptData block.
MAC
It is possible to also include a MAC value in the CryptData block. The MAC block consists of a Value (containing the MAC) and a KSN which is used to find the key used to calculate the MAC.
The following XML message represents an example of "CryptData" element:
<v1:EMVCardPresentRequest>
<v1:CryptData>
<v1:SRED>
<v1:Value>5d97165d423a409853a4be21d331771d8d6b42a9248e8ff1</v1:Value>
<v1:KSN>0186a8000003f0200010</v1:KSN>
</v1:SRED>
<v1:MAC>
<v1:Value>c61bce2665251dfb</v1:Value>
<v1:KSN>0186a2000003f0200010</v1:KSN>
</v1:MAC>
</v1:CryptData> …
Offline approval transaction
Offline transactions are supposed to be sent with OfflineApprovalType and approval code in ReferenceNumber.
EMV Data
The EMV information could be included either with tag-length-value format in TLVData or as XML elements under EMVRequestData. The following EMV tags are supported by the Gateway:
| EMV Tag | Request | Response | IPGAPI Element to EMVCardPresentRequest/EMVRequestData OR EMVCardPresentResponse/EMVResponseData | Format | Length |
|---|---|---|---|---|---|
| 4F | x | ApplicationIdentifier-4F | binary | 5-16 | |
| 50 | x | ApplicationLabel-50 | alphanumeric | 1-16 | |
| 5F2A | x | TransactionCurrencyCode-5F2A | numeric | 3 | |
| 5F34 | x | ApplicationPANSequenceNumber-5F34 | numeric | 2 | |
| 71 | x | IssuerScriptTemplate1-71 | binary | 9-746 | |
| 72 | x | IssuerScriptTemplate2-72 | binary | 9-746 | |
| 82 | x | ApplicationInterchangeProfile-82 | binary | 2 | |
| 84 | x | DedicatedFileName-84 | binary | 5-16 | |
| 8A | x | IssuerAuthorizationResponseCode-8A | alphanumeric | 2 | |
| 91 | x | IssuerAuthenticationData-91 | binary | 8-16 | |
| 91 | x | IssuerAuthenticationData-91 | binary | 8-16 | |
| 95 | x | TerminalVerificationResults-95 | binary | 5 | |
| 98 | x | TransactionCertificateHashValue-98 | binary | 20 | |
| 9A | x | TransactionDate-9A | numeric | 6 | |
| 9B | x | TransactionStatusInformation-9B | binary | 2 | |
| 9C | x | TransactionType-9C | numeric | 2 | |
| 9F02 | x | AmountAuthorised-9F02 | numeric | 12 | |
| 9F03 | x | AmountOther-9F03 ChargeTotal = SubTotal + ValueAddedTax + localTax + DeliveryAmount + CashbackAmount + TipAmount | numeric | 12 | |
| 9F06 | x | ApplicationIdentifierTerminal-9F06 | binary | 5-16 | |
| 9F07 | x | ApplicationUsageControl-9F07 | binary | 4 | |
| 9F09 | x | ApplicationVersionNumber-9F09 | binary | 2 | |
| 9F10 | x | IssuerApplicationData-9F10 | binary | 32 | |
| 9F16 | x | MerchantIdentifier-9F16 | alphanumeric | 16 | |
| 9F1A | x | TerminalCountry-9F1A | numeric | 2 | |
| 9F1E | x | InterfaceDeviceSerialNumber-9F1E | alphanumeric | 6 | |
| 9F21 | x | TransactionTime-9F21 | numeric | 6 | |
| 9F26 | x | ApplicationCryptogram-9F26 | binary | 8 | |
| 9F27 | x | CryptogramInformationData-9F27 | binary | 1 | |
| 9F33 | x | TerminalCapabilities-9F33 | binary | 3 | |
| 9F34 | x | CVMResults-9F34 | binary | 3 | |
| 9F35 | x | TerminalType-9F35 | numeric | 2 | |
| 9F36 | x | ApplicationTransactionCounter-9F36 | binary | 2 | |
| 9F37 | x | UnpredictableNumber-9F37 | binary | 4 | |
| 9F39 | x | PointOfServiceEntryMode-9F39 | numeric | 2 | |
| 9F40 | x | AdditionalTerminalCapabilities-9F40 | binary | 5 | |
| 9F41 | x | TransactionSequenceCounter-9F41 | numeric | 4-8 | |
| 9F49 | x | DynamicDataAuthenticationObjectList-9F49 | binary | 0-252 | |
| 9F53 | x | TransactionCategoryCode-9F53 | binary | 1 | |
| 9F67 | x | EMV-9F67 | binary | 1-32 | |
| 9F6E | x | EMV-9F6E | binary | 4-32 | |
| 9F7C | x | EMV-9F7C | binary | 1-32 |
EMV Request (using EMVRequestData)
The EMV information could be included as XML elements under EMVRequestData. The following XML document represents an example of a transaction request including EMVRequestData element:
<ipgapi:IPGApiOrderRequest
xmlns:v1="http://ipg-online.com/ipgapi/schemas/v1"
xmlns:ipgapi="http://ipg-online.com/ipgapi/schemas/ipgapi">
<v1:Transaction>
<v1:CreditCardTxType>
<v1:Type>sale</v1:Type>
</v1:CreditCardTxType>
<v1:EMVCardPresentRequest>
<v1:CryptData>
<v1:SRED>
<v1:Value>59E54F4798AFC82C09C93EA1D2757E8F7B9A4C5082F76041</v1:Value>
<v1:KSN>9A2133026261C0600001</v1:KSN>
</v1:SRED>
<v1:PINBlock>
<v1:Value>68XXXXXXXXXXXX26</v1:Value>
<v1:KSN>9A214A00000040800005</v1:KSN>
</v1:PINBlock>
</v1:CryptData>
<v1:EMVRequestData>
<v1:TerminalVerificationResults-95>0000000000</v1:TerminalVerificationResults-95>
<v1:PointOfServiceEntryMode-9F39>07</v1:PointOfServiceEntryMode-9F39>
<v1:ApplicationLabel-50>VISA CREDIT</v1:ApplicationLabel-50>
<v1:TransactionCurrencyCode-5F2A>978</v1:TransactionCurrencyCode-5F2A>
<v1:ApplicationPANSequenceNumber-5F34>01</v1:ApplicationPANSequenceNumber-5F34>
<v1:ApplicationInterchangeProfile-82>2000</v1:ApplicationInterchangeProfile-82>
<v1:DedicatedFileName-84>A0000000031010</v1:DedicatedFileName-84>
<v1:TransactionDate-9A>160422</v1:TransactionDate-9A>
<v1:TransactionType-9C>00</v1:TransactionType-9C>
<v1:AmountAuthorised-9F02>000000000900</v1:AmountAuthorised-9F02>
<v1:AmountOther-9F03>000000000000</v1:AmountOther-9F03>
<v1:ApplicationIdentifierTerminal-9F06>A0000000031010</v1:ApplicationIdentifierTerminal-9F06>
<v1:TerminalApplicationVersionNumber-9F09>0001</v1:TerminalApplicationVersionNumber-9F09>
<v1:IssuerApplicationData-9F10>06010A03A00000</v1:IssuerApplicationData-9F10>
<v1:TerminalCountry-9F1A>0300</v1:TerminalCountry-9F1A>
<v1:InterfaceDeviceSerialNumber-9F1E>000D1143</v1:InterfaceDeviceSerialNumber-9F1E>
<v1:ApplicationCryptogram-9F26>2891CDC96B987F0E</v1:ApplicationCryptogram-9F26>
<v1:CryptogramInformationData-9F27>80</v1:CryptogramInformationData-9F27>
<v1:TerminalCapabilities-9F33>E0F8C8</v1:TerminalCapabilities-9F33>
<v1:TerminalType-9F35>22</v1:TerminalType-9F35>
<v1:ApplicationTransactionCounter-9F36>034E</v1:ApplicationTransactionCounter-9F36>
<v1:UnpredictableNumber-9F37>8D8B26AD</v1:UnpredictableNumber-9F37>
<v1:TransactionSequenceCounter-9F41>00000038</v1:TransactionSequenceCounter-9F41>
<v1:CVMResults-9F34>040302</v1:CVMResults-9F34>
</v1:EMVRequestData>
</v1:EMVCardPresentRequest>
<v1:Payment>
<v1:ChargeTotal>9</v1:ChargeTotal>
<v1:Currency>978</v1:Currency>
</v1:Payment>
…
…
</v1:Transaction>
</ipgapi:IPGApiOrderRequest>
Please note, that our Gateway supports either eligible XML elements or TLVData for EMV transaction, a mixed form is not allowed.
The API response returned for Card Present request contains EMVCardPresentResponseelement. EMV data is included as XML elements in EMVResponseData as well as tag-value-length String in TLVData.
<ipgapi:IPGApiOrderResponse
xmlns:ipgapi="http://ipg-online.com/ipgapi/schemas/ipgapi"
xmlns:a1="http://ipg-online.com/ipgapi/schemas/a1"
xmlns:v1="http://ipg-online.com/ipgapi/schemas/v1">
...
...
<ipgapi:EMVCardPresentResponse>
<ipgapi:EMVResponseData>
<ipgapi:IssuerAuthenticationData-91>20FEC7E275ECF3E00012</ipgapi:IssuerAuthenticationData-91>
<ipgapi:IssuerScriptTemplate1-71>860D8424000008F0250E2304D91263</ipgapi:IssuerScriptTemplate1-71>
<ipgapi:IssuerAuthorizationResponseCode-8A>00</ipgapi:IssuerAuthorizationResponseCode-8A>
</ipgapi:EMVResponseData>
<v1:TLVData>910A20FEC7E275ECF3E000128A023030710F860D8424000008F0250E2304D91263
</v1:TLVData>
</ipgapi:EMVCardPresentResponse>
</ipgapi:IPGApiOrderResponse>
Contactless Single-Tap
IPGApiOrderResponse returned for Card Present request contains additional “EMVCardPresentResponse” element. EMV data is included as XML elements in EMVResponseData as well as tag.
All acquirers and merchants in the Europe are required to follow the contactless terminal implementation guidelines, which have been updated to facilitate compliance with the European Banking Authority (EBA)’s strong customer authentication (SCA) requirements, based on the revised Payments Service Directive (PSD2) provisions.
As defined in PSD2 SCA requirements, issuers may decline contactless transactions without CVM when new thresholds will be reached and send back specific response codes to drive the terminal behavior.
The decline response codes returned by the issuer/host system may be represented by:
• The content of xml field ProcessorResponseCode
• The content of xml field IssuerAuthorizationResponseCode-8A
• EMV tag 8A within TLVData element
Terminals supporting Contactless Single-TAP PIN request must send an additional EMV tag DF8301 to indicate the contactless (Bit8) and contactless single tap (Bit7) capabilities:
| EMV Tag | Additional Terminal Read Capabilities | Format | Length |
|---|---|---|---|
| DF8301 | Bit8 contactless capability • If 1, terminal can read contactless cards Bit7 contactless single tap PIN capability • if 1, terminal can read contactless single tap Bit 5 & 6 PIN Capability • if 00 - undefined (hardware PIN capable per default) • if 01 - hardware PIN capable • if 10 - PIN not capable • if 11 - software PIN capable Bit 3 & 4 mPOS / SoftPOS Indicator: • if 00 - undefined • if 01 - SoftPOS terminal (phone / tablet NFC as card capture capability) • if 10 - mPos but not SoftPOS (mPos terminal with PCI compliant card reader) • if 11 - not mPOS / not SoftPOS, traditional POS Bit 1-2: (reserved for future use) • 00 | binary | 1 |
Example:
DF83010101 for terminal contactless capable but does not support contactless single tap PIN
DF83010103 for terminal contactless capable and supports contactless single tap PIN
Based on the response code and ContactlessSingleTapPIN indicator returned by the host system, the Gateway may additionally include PINRequestType back to the terminal as part of IPGApi response:
<ipgapi:IPGApiOrderResponse xmlns:ipgapi="http://ipg-online.com/ipgapi/schemas/ipgapi" xmlns:a1="http://ipg-online.com/ipgapi/schemas/a1" xmlns:v1="http://ipg-online.com/ipgapi/schemas/v1">
...
...
<v1: PINRequestType>ContactlessSingleTapPIN</v1: PINRequestType>
<!-- or <v1:PINRequestType>FallbackToChipAndPIN</v1:PINRequestType> -->
....
</ipgapi:IPGApiOrderResponse>
In case the element PINRequestType is returned with the value "ContactlessSingleTapPIN", the terminal will need to re-send the transaction with original chip data, but this time include (online) PIN, new transaction reference and additional keyValuePair element:
...
<Transaction>
<TransactionDetails>
<AdditionalRequestParameters>
<keyValuePair>
<key>PINRequestType</key>
<value>ContactlessSingleTapPIN</value>
</keyValuePair>
</AdditionalRequestParameters>
</TransactionDetails>
<Transaction>
....
Please note, that the Gateway does not validate if the “ContactlessSingleTapPIN” indicator has been sent together with Online PIN, it is the responsibility of the terminal to provide the consistent data.
EFTPOS processing
EFTPOS is Australian debit card scheme available for card present and e-commerce processing. In order to process Card Present EFTPOS transaction, you must include additional element CardAccountTypein your API request.
<xs:simpleType name="CardAccountType">
<xs:restriction base="xs:string">
<xs:enumeration value="saving" />
<xs:enumeration value="checking" />
</xs:restriction>
</xs:simpleType>
We highly recommend to submit also additional optional EMV TLV Data in your API request:
| EMV Tag | Request | Response | IPGAPI Element to EMVCardPresentRequest/EMVRequestData OR EMVCardPresentResponse/EMVResponseData | Format | Length |
|---|---|---|---|---|---|
| 9F19 | x | TokenRequestorId-9F19 | numeric | 6 | |
| 9F66 | x | TerminalTransactionQualifiers-9F66 | binary | 4 | |
| 9F6E | x | EMV-9F6E | binary | 4-32 | |
| 9F24 | x | PaymentAccountReference-9F24 | alphanumeric | 29 | |
| DF8303 | x | AdditionalRoutingInfo-DF8303 | binary | 1 |
The following XML document represents an example of a Sale transaction using the minimum set of elements:
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ipg="http://ipg-online.com/ipgapi/schemas/ipgapi" xmlns:pay="http://api.clickandbuy.com/webservices/pay_1_0_0/" xmlns:v1="http://ipg-online.com/ipgapi/schemas/v1">
<soapenv:Header/>
<soapenv:Body>
<ipg:IPGApiOrderRequest>
<v1:Transaction>
<v1:CreditCardTxType>
<v1:StoreId>123456789</v1:StoreId>
<v1:Type>sale</v1:Type>
</v1:CreditCardTxType>
<v1:EMVCardPresentRequest>
<v1:CryptData>
<v1:SRED>
<v1:Value>3d0923050665321fd90d73dcae22ccf2de8948e078b6fadf7d6531b3e24b5057</v1:Value>
<v1:KSN>0000096c7372db0367a9</v1:KSN>
</v1:SRED>
</v1:CryptData>
<v1:TLVData>9F6604000040009F2701809F1A0200369F1906006110030273840cA000000384100001000000039F060cA000000384100001000000035F3401019F37041CBFC9259F3303A0F8C89F2608A023F78A7D6374199F21030539449F10200FA501A80000020000000000000000000F0E21C1006110030273F100000000009F090201009F6E0a0121C1006110030273819F34030100029F02060000000005509C01009A03240201950500000000009F360200459F350122820219005F2A0200369F390107DF830101039F0306000000000000</v1:TLVData>
</v1:EMVCardPresentRequest>
<v1:cardAccount>saving</v1:cardAccount>
<v1:Payment>
<v1:ChargeTotal>5.50</v1:ChargeTotal>
<v1:Currency>AUD</v1:Currency>
</v1:Payment>
<v1:TransactionDetails>
<v1:OrderId>TEFDKCCZAA</v1:OrderId>
<v1:Terminal>
<v1:TerminalID>80000727</v1:TerminalID>
</v1:Terminal>
</v1:TransactionDetails>
</v1:Transaction>
</ipg:IPGApiOrderRequest>
</soapenv:Body>
</soapenv:Envelope>
The following XML document represents an example of a response from the Gateway:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<ipgapi:IPGApiOrderResponse xmlns:a1="http://ipg-online.com/ipgapi/schemas/a1" xmlns:ipgapi="http://ipg-online.com/ipgapi/schemas/ipgapi" xmlns:v1="http://ipg-online.com/ipgapi/schemas/v1">
<ipgapi:ApprovalCode>Y:015695:7289762718:PPX :403121525922</ipgapi:ApprovalCode>
<ipgapi:AVSResponse>PPX</ipgapi:AVSResponse>
<ipgapi:Brand>EFTPOS</ipgapi:Brand>
<ipgapi:Country>AUS</ipgapi:Country>
<ipgapi:CommercialServiceProvider>SERVICE_PROVIDER</ipgapi:CommercialServiceProvider>
<ipgapi:OrderId>TEFDKCCZAA</ipgapi:OrderId>
<ipgapi:IpgTransactionId>77289762718</ipgapi:IpgTransactionId>
<ipgapi:PaymentType>CREDITCARD</ipgapi:PaymentType>
<ipgapi:ProcessorApprovalCode>015695</ipgapi:ProcessorApprovalCode>
<ipgapi:ProcessorReferenceNumber>403121525922</ipgapi:ProcessorReferenceNumber>
<ipgapi:ProcessorResponseCode>00</ipgapi:ProcessorResponseCode>
<ipgapi:ProcessorResponseMessage>Function performed error-free</ipgapi:ProcessorResponseMessage>
<ipgapi:TDate>1706737190</ipgapi:TDate>
<ipgapi:TDateFormatted>2024.02.01 03:09:50 (IST)</ipgapi:TDateFormatted>
<ipgapi:TerminalID>80000727</ipgapi:TerminalID>
<ipgapi:TransactionResult>APPROVED</ipgapi:TransactionResult>
<ipgapi:TransactionTime>1706737190</ipgapi:TransactionTime>
<ipgapi:EMVCardPresentResponse>
<ipgapi:EMVResponseData>
<ipgapi:IssuerAuthorizationResponseCode-8A>00</ipgapi:IssuerAuthorizationResponseCode-8A>
</ipgapi:EMVResponseData>
<v1:TLVData>8A023030</v1:TLVData>
</ipgapi:EMVCardPresentResponse>
<ipgapi:IssuerReferenceNumber>403121525922</ipgapi:IssuerReferenceNumber>
</ipgapi:IPGApiOrderResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Updated 7 months ago
