Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
developer:api_specification:xml_payment_features [2019/12/12 13:20] robinc [Examples for a Request] Added ND008 |
developer:api_specification:xml_payment_features [2019/12/12 13:29] robinc [Response Body Fields] Added BRANDTXIDENTIFIER field |
||
|---|---|---|---|
| Line 316: | Line 316: | ||
| Two usages: | Two usages: | ||
| - | * Processing transaction with Secure Card (stored in Nuvei Gateway) but using the same Secure Card for different usage. | + | * * Processing transaction with Secure Card (stored in Nuvei Gateway) but using the same Secure Card for different usage. |
| - | * Processing transaction in clear card but token vaulted externally (outside Nuvei Gateway). | + | * * Processing transaction in clear card but token vaulted externally (outside Nuvei Gateway). |
| These fields will only be used on a payment if you have secure card storage enabled. The fields will have the following behavior: Hidden - the gateway accepts the fields, if sent, and add them to the transaction, but does not show it to the customer. | These fields will only be used on a payment if you have secure card storage enabled. The fields will have the following behavior: Hidden - the gateway accepts the fields, if sent, and add them to the transaction, but does not show it to the customer. | ||
| Line 329: | Line 329: | ||
| \\ | \\ | ||
| - | |||
| Quick example: | Quick example: | ||
| + | <code xml> | ||
| + | <?xml version="1.0" encoding="UTF-8"?> | ||
| + | <PAYMENT> | ||
| + | <ORDERID>CSV_99769707</ORDERID> | ||
| + | <TERMINALID>2366006</TERMINALID> | ||
| + | <AMOUNT>6.00</AMOUNT> | ||
| + | <DATETIME>11-09-2019:14:02:49:708</DATETIME> | ||
| + | <CARDNUMBER>4444333322221111</CARDNUMBER> | ||
| + | <CARDTYPE>VISA</CARDTYPE> | ||
| + | <CARDEXPIRY>1224</CARDEXPIRY> | ||
| + | <CARDHOLDERNAME>na</CARDHOLDERNAME> | ||
| + | <HASH>f048c44d0340af522d5796110675fb1a</HASH> | ||
| + | <CURRENCY>USD</CURRENCY> | ||
| + | <TERMINALTYPE>1</TERMINALTYPE> | ||
| + | <TRANSACTIONTYPE>1</TRANSACTIONTYPE> | ||
| + | <AUTOREADY>Y</AUTOREADY> | ||
| + | <CVV>123</CVV> | ||
| + | <ADDRESS1>ads</ADDRESS1> | ||
| + | <ADDRESS2>ads2</ADDRESS2> | ||
| + | <POSTCODE>123</POSTCODE> | ||
| + | <CREDENTIALONFILE> | ||
| + | <ORIGINALBRANDTXIDENTIFIER>1234567890</ORIGINALBRANDTXIDENTIFIER> | ||
| + | <STOREDCREDENTIALTXTYPE>SUBSEQUENT_MERCHANT_INITIATED_TXN</STOREDCREDENTIALTXTYPE> | ||
| + | <STOREDCREDENTIALUSE>UNSCHEDULED</STOREDCREDENTIALUSE> | ||
| + | </CREDENTIALONFILE> | ||
| + | </PAYMENT> | ||
| + | </code> | ||
| ==== Response Body Fields ==== | ==== Response Body Fields ==== | ||
| Line 347: | Line 373: | ||
| | CVVRESPONSE | The result of the CVV check. Check **[[merchant:existing_merchant:other_information:transaction_responses|Transaction Responses]]**. | | | CVVRESPONSE | The result of the CVV check. Check **[[merchant:existing_merchant:other_information:transaction_responses|Transaction Responses]]**. | | ||
| | PROCESSINGTERMINAL | If the transaction was performed on a "routing terminal" then this is populated with processing terminal ID that the system selected to process the transaction.| | | PROCESSINGTERMINAL | If the transaction was performed on a "routing terminal" then this is populated with processing terminal ID that the system selected to process the transaction.| | ||
| - | | FRAUDREVIEWRESPONSE | Component of the response that is going to be added in case the Threat Metrix feature is in use for the Terminal processing the Payment. See **ND002 - ThreatMetrix Response** for more details. | | + | | FRAUDREVIEWRESPONSE | Component of the response that is going to be added in case the Threat Metrix feature is in use for the Terminal processing the Payment. See **ND002 - Sentinal Defense Response** for more details. | |
| | ADDITIONAL_FIELD | This field is used to send back data of interest of the merchant received by the gateway during the transaction. See **ND003 - Additional Information on Response**| | | ADDITIONAL_FIELD | This field is used to send back data of interest of the merchant received by the gateway during the transaction. See **ND003 - Additional Information on Response**| | ||
| | CARDREFERENCE | This field represents the token generated for the Secure Card. It's going to be returned when the Settings related to this payment enable the automatic generation of Secure Cards within a Payment. Take a look at **ND004 - Secure Card Auto Registration**. | | | CARDREFERENCE | This field represents the token generated for the Secure Card. It's going to be returned when the Settings related to this payment enable the automatic generation of Secure Cards within a Payment. Take a look at **ND004 - Secure Card Auto Registration**. | | ||
| Line 353: | Line 379: | ||
| | DATETIME | Response date and time for the transaction, created by the bank. Format: YYYY-MM-DDTHH:MM:SS. Note that this is intentionally in a different format to the request timestamp to highlight the fact that it is a different time.| | | DATETIME | Response date and time for the transaction, created by the bank. Format: YYYY-MM-DDTHH:MM:SS. Note that this is intentionally in a different format to the request timestamp to highlight the fact that it is a different time.| | ||
| | HASH | 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 | A HASH code formed by part of the request fields. The formation rule is given at the **ND001 - Hash Formation**, in the next section. | | ||
| + | | BRANDTXIDENTIFIER | The gateway returns the transaction identifier received from Acquirer to the merchant in the response if Credential on File is used. | | ||
| </searchtable> | </searchtable> | ||
| \\ | \\ | ||