Last active
June 26, 2024 07:33
-
-
Save f0-x/9756a1dcb2de9354f0fb93375137de1a to your computer and use it in GitHub Desktop.
Response Format for check-limit POST API.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
{ | |
"success": true | false, | |
"status_code": 403 | 200, | |
"message": "Payment limit exceeded" | "Payment can be processed", | |
"payload": [ | |
{ | |
"limit_exceeds": true | false, | |
// 'message' is null when none of the limits are exceeded | |
"message": string | null, | |
"method_id": 34 | 35 | 36 | 37, | |
//How much is the "CDS Daily Cash Payment Limit" OR "EFTPOS Daily Machine Limit" has been reached for the given Customer ? | |
// is 'null' if the limit isn't set | |
"daily_transaction_limit_reached": "2259.83" | null | |
// What's the CDS Tag Transaction Limit for the current location ? | |
// is 'null' if it's not exceeded | |
"cds_tag_transaction_limit": "10.00" | null, | |
// "EFTPOS Transaction Limit" is present too, this limit 'might be' required for other payment methods too | |
// in future i.e "EFT Transaction Limit", "ECD Transaction Limit" etc. | |
// is 'null' when the single transaction limit isn't exceeded. | |
"single_transaction_limit": "400.00" | null, | |
} | |
] | |
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment