Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
developer:api_specification:xml_3d_secure [2018/05/25 17:35]
127.0.0.1 external edit
developer:api_specification:xml_3d_secure [2019/07/02 08:06]
thiago123 PSD2 changes
Line 4: Line 4:
  
 \\ \\
-To simplify 3D Secure integration using XML payments, %CompanyName provides a simple MPI redirect. To allow 3D Secure transactions ​for a terminal ​it should ​be configured ​and registered with the card schemes, please ​contact the %CompanyName support team for details.+To simplify 3D Secure integration using the XML payments ​API, %CompanyName provides a simple MPI redirect. ​\\ 
 + 
 +<WRAP center important 100%> 
 +**3D SECURE ENABLING** 
 + 
 +To allow 3D Secure transactions ​on one of your terminal ​accounts, this feature and its settings must be configured. Please ​contact the %CompanyName support team in case you need the activation of this feature. 
 +</​WRAP>​ 
 + 
 +<WRAP center important 100%> 
 +**PSD2 and String Customer Authentication (SCA)** 
 + 
 +The Payment Services Directive 2 (PSD2) comes into force in 2019 (only applicable in EU) and you might need to be prepared to provide SCA for your payments. Take a closer look at our **[[https://​worldnettps.com/​psd2-faq/​|F.A.Q]]** in case you have more questions. 
 +</​WRAP>​ 
 +\\
  
 The following resources are the same for all the requests and responses you find in this page: The following resources are the same for all the requests and responses you find in this page:
Line 13: Line 26:
  
 <WRAP center important 100%> <WRAP center important 100%>
-This URL should be used in test mode only. Please contact the %CompanyName support team to receive the live URL.+**3D SECURE LIVE** 
 + 
 +This URL should be used in test mode only.  
 +Please contact the %CompanyName support team to receive the live URL.
 </​WRAP>​ </​WRAP>​
  
-The Card Holder ​will have to pass the 3D Secure ​check, and the check result will be sent back to the Merchant'​s application as a GET request. ​Processing ​result response will return the **MPIREF** parameter, which should be included in the XML payment request.+The 3D Secure verification is going to require that the Card Holder pass an identity ​check, and the check result will be sent back to the Merchant'​s application as a GET request. ​The processing ​result response will return the **MPIREF** parameter, which should be included in the XML payment request. 
 + 
 +After the merchant application receives the 3D Secure check result, it should send an XML payment request. ​
  
-After the merchant application receives the 3D Secure check result, it should send an XML payment request. ​If the 3D Secure check was successful (‘A’ Result) the payment request should contain the fields MPIREF, Order ID and Terminal ID and they should be the same as in the 3D Secure request. ​+If the 3D Secure check was successful (‘A’ Result) the payment request should contain the fields MPIREF, Order ID and Terminal ID and they should be the same as in the 3D Secure request.
  
 If the 3D Secure check was not successful (‘D’ Result) the application can send a non-3D Secure transaction (MPIREF will not be available in such case) or don’t send payment transaction at all.  If the 3D Secure check was not successful (‘D’ Result) the application can send a non-3D Secure transaction (MPIREF will not be available in such case) or don’t send payment transaction at all. 
Line 33: Line 51:
 ^ **FIELD** ^ **REQUIRED** ^ **DESCRIPTION** ^ ^ **FIELD** ^ **REQUIRED** ^ **DESCRIPTION** ^
 | TERMINALID ​ | Y | A Terminal ID provided by %CompanyName. NB - Please contact %CompanyName to be issued with a test terminal ID.  | | TERMINALID ​ | Y | A Terminal ID provided by %CompanyName. NB - Please contact %CompanyName to be issued with a test terminal ID.  |
-| CARDNUMBER ​ | Y | The payment card number. ​                                                                                       +| CARDNUMBER ​ | Y | The payment card number. | 
-| CARDEXPIRY ​ | Y | 4 digit expiry field (MMYY). ​                                                                                   +| CARDEXPIRY ​ | Y | 4 digit expiry field (MMYY). | 
-| CARDTYPE ​   | Y | See **[[developer:​api_specification:​special_fields_and_parameters#​the_card_types| Card Types]]** section. ​                     +| CARDTYPE ​   | Y | See **[[developer:​api_specification:​special_fields_and_parameters#​the_card_types| Card Types]]** section. | 
-| AMOUNT ​     | Y | The amount of the transaction as a 2 digit decimal or an Integer value for JPY amounts. ​                        ​+| AMOUNT ​     | Y | The amount of the transaction as a 2 digit decimal or an Integer value for JPY amounts. | 
-| CURRENCY ​   | Y | A 3 character currency code of the transaction. ​                                                                ​+| CURRENCY ​   | Y | A 3 character currency code of the transaction. | 
-| ORDERID ​    | Y | A unique identifier for the order created by the merchant (Max 24 characters). ​                                 +| ORDERID ​    | Y | A unique identifier for the order created by the merchant (Max 24 characters). | 
-| CVV         | N | The security code entered by the card holder. ​                                                                  ​|+| CVV         | N | The security code entered by the card holder. |
 | DATETIME |  Y  | Request date and time. Format: DD-MM-YYYY:​HH:​MM:​SS:​SSS. | | DATETIME |  Y  | Request date and time. Format: DD-MM-YYYY:​HH:​MM:​SS:​SSS. |
 | HASH |  Y  | A HASH code formed by part of the request fields. The formation rule is given at the **ND001 - Hash Formation**,​ in the next section. | | HASH |  Y  | A HASH code formed by part of the request fields. The formation rule is given at the **ND001 - Hash Formation**,​ in the next section. |
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International