Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
developer:api_specification:xml_payment_features [2021/04/13 13:02] robinc [Request Body Fields] added ORDERID field info |
developer:api_specification:xml_payment_features [2022/03/04 11:30] lezlieh edits for secure token |
||
|---|---|---|---|
| Line 31: | Line 31: | ||
| | DATETIME | Y | Request date and time. Format: DD-MM-YYY:HH:MM:SS:SSS.| | | DATETIME | Y | Request date and time. Format: DD-MM-YYY:HH:MM:SS:SSS.| | ||
| | TRACKDATA | N | Track 2 data.\\ Should be present for a swiped cardholder present (CHP) transaction. If this is present then TERMINALTYPE should be set to 3 and TRANSACTIONTYPE should be set to 0. | | | TRACKDATA | N | Track 2 data.\\ Should be present for a swiped cardholder present (CHP) transaction. If this is present then TERMINALTYPE should be set to 3 and TRANSACTIONTYPE should be set to 0. | | ||
| - | | CARDNUMBER | N | Payment card number.\\ Required if TRACKDATA is not being sent.\\ If a SECURECARD is used (in CARDTYPE), this field should inform the CARDREFERENCE of the given Secure Card. | | + | | CARDNUMBER | N | Payment card number.\\ Required if TRACKDATA is not being sent.\\ If a SECURECARD is used (in CARDTYPE), this field should inform the CARDREFERENCE of the given Secure Token. | |
| | GOOGLEPAYLOAD | N | When using google pay for payments, instead of the TRACKDATA or CARDNUMBER, you pass this field, with the Google Pay user data, received from your request, converted to Hexadecimal. | | | GOOGLEPAYLOAD | N | When using google pay for payments, instead of the TRACKDATA or CARDNUMBER, you pass this field, with the Google Pay user data, received from your request, converted to Hexadecimal. | | ||
| | APPLEPAYLOAD | N | When using apple pay for payments, instead of the TRACKDATA or CARDNUMBER, you pass this field, with the Apple Pay user data, received from your request, converted to Hexadecimal. | | | APPLEPAYLOAD | N | When using apple pay for payments, instead of the TRACKDATA or CARDNUMBER, you pass this field, with the Apple Pay user data, received from your request, converted to Hexadecimal. | | ||
| - | | CARDTYPE | Y | Card Type used for the transaction.\\ For more details on this, visit **[[developer:api_specification:special_fields_and_parameters#the_card_types|Special Fields and Parameters - Card Types]]**.\\ This field can also admit the SECURECARD type, when using a Secure Card to perform the transaction. | | + | | CARDTYPE | Y | Card Type used for the transaction.\\ For more details on this, visit **[[developer:api_specification:special_fields_and_parameters#the_card_types|Special Fields and Parameters - Card Types]]**.\\ This field can also admit the SECURECARD type, when using a Secure Token to perform the transaction. | |
| | CARDEXPIRY | N | Expiry date of the card.\\ A 4 digit expiry field (MMYY), required if TRACKDATA is not being sent.\\ This field should not be informed if the CARDTYPE is SECURECARD. | | | CARDEXPIRY | N | Expiry date of the card.\\ A 4 digit expiry field (MMYY), required if TRACKDATA is not being sent.\\ This field should not be informed if the CARDTYPE is SECURECARD. | | ||
| | CARDHOLDERNAME | N | The name of the card holder, required if TRACKDATA is not being sent and not using a SecureCard. It should be as displayed on the front of the card.\\ This field should not be informed if the CARDTYPE is SECURECARD. | | | CARDHOLDERNAME | N | The name of the card holder, required if TRACKDATA is not being sent and not using a SecureCard. It should be as displayed on the front of the card.\\ This field should not be informed if the CARDTYPE is SECURECARD. | | ||
| Line 2419: | Line 2419: | ||
| The general rule to build the HASH field is given on the **[[developer:api_specification:special_fields_and_parameters|Special Fields and Parameters]]** page, under the **[[developer:api_specification:special_fields_and_parameters#the_hash_parameter|Special Fields and Parameters]]** section. For this specific feature, you should use the following formats: | The general rule to build the HASH field is given on the **[[developer:api_specification:special_fields_and_parameters|Special Fields and Parameters]]** page, under the **[[developer:api_specification:special_fields_and_parameters#the_hash_parameter|Special Fields and Parameters]]** section. For this specific feature, you should use the following formats: | ||
| + | |||
| + | **When using UNIQUEREF** | ||
| <WRAP center box 100%> | <WRAP center box 100%> | ||
| TERMINALID:UNIQUEREF:DATETIME:SECRET | TERMINALID:UNIQUEREF:DATETIME:SECRET | ||
| + | </WRAP> | ||
| + | **When using ORDERID** | ||
| + | <WRAP center box 100%> | ||
| + | TERMINALID:ORDERID:DATETIME:SECRET | ||
| </WRAP> | </WRAP> | ||
| Line 2446: | Line 2452: | ||
| </code> | </code> | ||
| + | <code xml> | ||
| + | <?xml version="1.0" encoding="UTF-8"?> | ||
| + | <GET_TRANSACTION_DETAILS> | ||
| + | <TERMINALID>6491002</TERMINALID> | ||
| + | <ORDERID>GCNQAWUUVZ</ORDERID> | ||
| + | <DATETIME>06-03-2018:17:41:08:273</DATETIME> | ||
| + | <HASH>73e340cfb2b7424252d1ced917e4f74704aaa66a9600039f4800434cefe87d721c342d2b915c6e2aeea88b34e749ba97665f7d9e50b1144ca0f0745361fc4896</HASH> | ||
| + | </GET_TRANSACTION_DETAILS> | ||
| + | </code> | ||
| \\ | \\ | ||
| ==== Response Body Fields ==== | ==== Response Body Fields ==== | ||
| Line 2485: | Line 2500: | ||
| <WRAP center box 100%> | <WRAP center box 100%> | ||
| - | TERMINALID:UNIQUEREF:ORDERID:TRANSACTION_STATUS:TRANSACTION_DATE:OPERATOR:TRANSACTION_TYPE:CURRENCY:AUTHORIZEDAMOUNT:BATCH_NUMBER:BULK_NUMBER:PROCESSINGTERMINAL:RESPONSECODE:RESPONSETEXT:APPROVALCODE:CARDCURRENCY:CARDAMOUNT:CONVERSIONRATE:DESCRIPTION:DATETIME:SECRET | + | TERMINALID:UNIQUEREF:TRANSACTION_STATUS:TRANSACTION_DATE:OPERATOR:TRANSACTION_TYPE:CURRENCY:AUTHORIZEDAMOUNT:BATCH_NUMBER:BULK_NUMBER:PROCESSINGTERMINAL:RESPONSECODE:RESPONSETEXT:APPROVALCODE:CARDCURRENCY:CARDAMOUNT:CONVERSIONRATE:DESCRIPTION:DATETIME:SECRET |
| </WRAP> | </WRAP> | ||