Send Receipt
Requests to this API should only be made when a temporary value is used as the x_pos_transaction_ref in calls to ProcessAuthorisation. Humm will store the specified x_receipt_number, which it will use for transaction reconciliation in any future requests to ProcessSalesAdjustment.
Method: SendReceipt
Receipt
| Parameter | Type | Length | Description |
|---|---|---|---|
| x_pos_transaction_ref | Unicode string | 64 | This must be the same reference used in ProcessAuthorisation request. |
| x_merchant_id | Unicode string | 10 | Merchant identifier as defined by humm |
| x_device_id | Unicode string | 64 | Unique device identifier for the POS terminal |
| x_operator_id | Unicode string | 64 | ID of POS/terminal operator |
| x_firmware_version | Unicode string | 64 | Current firmware version of POS device |
| x_receipt_number | Unicode string | 64 | This must be the same reference (x_pos_transaction_ref) that would get passed through on future ProcessSalesAdjustment requests |
tracking_data optional | Associative array | Max 1000000 | A map that can be populated with additional tracking/state information that will get passed back in the response |
| signature | Hex string case-insensitive | 200 | Payload that is signed using HMAC-SHA256 using a device specific key |
Response
| Parameter | Type | Description |
|---|---|---|
| x_status | Unicode string | Success/Failure/Error |
| x_code | Unicode string | A code that maps to a specific reason |
| x_message | Unicode string | A string explaining the status/code above. |
| tracking_data | Associative array | Echoes tracking_data sent on the request |
| signature | Hex string case-insensitive | Payload that is signed using HMAC-SHA256 using a device specific key |
Testing
The following describes dummy API requests that return a predictable response. Please contact [email protected] to get access to the test/dummy APIs.
| Request -> x_receipt_number | Response -> x_status | Response -> x_code |
|---|---|---|
| 01###### | Success | SSER01 |
| 10###### | Failed | FSER01 |
| 11###### | Failed | FSER02 |
| 30###### | Error | EVAL01 |
| 31###### | Error | EAUT01 |
| any other value | Error | EISE01 |
Info
"#" signifies an alphanumeric digit
Testing Assumptions To generate the signature, use a device-signing-key of "1234567890". A invalid signature will cause an ESIG01 Error.
Updated 6 months ago