Maximum Debit Value On Invoices

This change is an important part of Ezypay's overall Fraud & Compliance activities. Previously, we relied upon transaction monitoring to alert us to transactions above the allowed limits (after the fact). Given the evolving complexities and volume of the transactions on our platform, it is critical we prevent these transactions from occurring.

We do not foresee any impact on your current integration, but please ensure that you provide the validation message to the merchant so that a lower amount can be entered and retried.

This change is implemented for both our sandbox and production environments.

Release Date

1st September 2020

New Changes

We have updated the Create Invoice API (Ad-Hoc) and Checkout Pages to add extra validation to the AMOUNT field to check against a merchant's Maximum Debit Value (MDV).

These updates apply to all regions for all ad-hoc created invoices and Checkout Page transactions (note that this does not yet apply to subscription payments).

Attempted invoices that are greater than a merchant's Maximum Debit Value will be rejected. You will receive an HTTP error 400 if the total invoice amount is over the configured Maximum Debit Value.

The payload message of the validation error will be as follows:

"type": "invalid_request_error",

"code": "invoice_exceeds_merchant_maximum_debit_value",

"message": "Total invoice amount (excluding Ezypay fees) exceeds this merchant's maximum debit value. Please retry with a lower amount"

The message needs to be visible to the merchants, to allow merchants the chance to change the invoice amount before proceeding to create a new invoice. For our Checkout Pages, the validation message will be displayed on the Checkout Page and the customer will not be able to proceed with the transaction.

Link to Relevant Documentation