Authorization holds configuration
We strongly recommend that you use an end-to-end test to test any configuration changes in your sandbox environment before implementing them in your production environment.
The end-to-end test should check that the hourly Authorization Holds Expiration (AUTHORIZATION_HOLDS_EXPIRATION) cron job expires the correct authorization holds. For more information, see Hourly authorization holds cron job in our User Guide.
If, to perform your end-to-end test you have to set holds in the past, then please contact us through Mambu Support so that we can assist you with manipulating the data directly in the database.
Retrieve and update the configuration for authorization holds.
An authorization hold is a standard practice with debit or a credit card transactions to hold a given balance as unavailable for the card holder until either the merchant settles the transaction, cancels the hold, or it expires. Using this endpoint you can configure the default authorization hold expiry for your organization as well as per merchant or merchant type using a Merchant Category Code (MCC). For more information about this resource, see Authorization Holds Configuration in our User Guide.
Your user or API consumer must have the View Manage Configuration As Code (GET_MANAGE_CONFIGURATION_AS_CODE) and/or Update Manage Configuration As Code (PUT_MANAGE_CONFIGURATION_AS_CODE) permissions to make GET and/or PUT requests to these configuration as code (CasC) endpoints. For more information about CasC, see Configuration as Code Overview.