Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
developer:api_specification:hpp_bulk_payments_features [2018/09/20 13:28] 127.0.0.1 external edit |
developer:api_specification:hpp_bulk_payments_features [2022/07/15 15:23] (current) |
||
|---|---|---|---|
| Line 88: | Line 88: | ||
| | CURRENCY | Y | ISO 4217 Currency Code. | | | CURRENCY | Y | ISO 4217 Currency Code. | | ||
| | AMOUNT | Y | Amount formatted to two decimal places. E.g. 1653.00 | | | AMOUNT | Y | Amount formatted to two decimal places. E.g. 1653.00 | | ||
| - | | CARDNUMBER | Y | Card PAN.\\ If a SECURECARD is used (in CARDTYPE), this field should inform the CARDREFERENCE of the given Secure Card. | | + | | CARDNUMBER | Y | Card PAN.\\ If a SECURECARD is used (in CARDTYPE), this field should inform the CARDREFERENCE of the given Secure Token. | |
| - | | CARDTYPE | Y | Card Type used for the transaction.\\ For more details 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 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 he card.A 4 digit expiry field (MMYY), required if the CARDTYPE is not SECURECARD.\\ If the CARDTYPE is SECURECARD this field shouldn't be informed. | | | CARDEXPIRY | N | Expiry date of he card.A 4 digit expiry field (MMYY), required if the CARDTYPE is not SECURECARD.\\ If the CARDTYPE is SECURECARD this field shouldn't be informed. | | ||
| | CARDHOLDERNAME | N | The cardholders name. Required if the CARDTYPE is not SECURECARD.\\ If the CARDTYPE is SECURECARD this field shouldn't be informed. | | | CARDHOLDERNAME | N | The cardholders name. Required if the CARDTYPE is not SECURECARD.\\ If the CARDTYPE is SECURECARD this field shouldn't be informed. | | ||
| Line 191: | Line 191: | ||
| The response of a file submission is quite simple. A String is returned in a CSV file to represent the result of the submission. | The response of a file submission is quite simple. A String is returned in a CSV file to represent the result of the submission. | ||
| - | In case of success, the code 200 and the BULKID are returned as a one line CSV file to ypur request (E.g. “200”,”76528”). This is important, once you need the BULKID field when requesting the result of your bulk processing. | + | In case of success, the code 200 and the BULKID are returned as a one line CSV file to your request (E.g. “200”,”76528”). This is important, once you need the BULKID field when requesting the result of your bulk processing. |
| * **Response Code**: Code defining the result of the bulk payment submission. the code is a 3 digit numeric code. | * **Response Code**: Code defining the result of the bulk payment submission. the code is a 3 digit numeric code. | ||
| Line 230: | Line 230: | ||
| ^ **TYPE** ^ **REQUEST URL** ^ | ^ **TYPE** ^ **REQUEST URL** ^ | ||
| - | | Bulk Payment Submit | %URLBulkPaymentsResult | | + | | Bulk Payment Result | %URLBulkResultPayments | |
| \\ | \\ | ||
| \\ | \\ | ||
| Line 308: | Line 308: | ||
| * **2**. The AMOUNT is formatted using minor units based on the CURRENCY and then rounded to 2 decimals. | * **2**. The AMOUNT is formatted using minor units based on the CURRENCY and then rounded to 2 decimals. | ||
| \\ | \\ | ||
| + | |||