Dec 11, 17:07 UTC
This incident has been resolved.
Dec 7, 15:31 UTC
We fixed the issue and deployed version v8.12 via an urgent minor release on the 4th of December 2018.
All deposit transactions with required custom fields for specific transaction channels can again be posted via API v1.0 and all non-required custom fields are stored in the database.
We are currently in the process of compiling a list of deposit transactions for affected tenants to remediate any data loss.
If you are an affected tenant, our Customer Support Team will reach out to you shortly.
For any questions and issues, please do not hesitate to reach out to email@example.com
Dec 5, 10:20 UTC
We identified an issue that is impacting deposit transactions custom fields posted with API v1.0 if the custom fields are marked as not required - the transaction is posted but without any custom fields being stored in the database.
Our development team has implemented a fix and is currently doing all the preparatory steps for the release, such as merging and testing the solution. We expect by end of day to release into production, if not latest tomorrow morning.
In the meantime, as a temporary workaround, we suggest performing a second PATCH request after posting Deposit transaction to add the custom fields values.
We are currently investigating the extent of any data loss. We have compiled a list of affected tenants, which will be contacted privately in order to perform remediation steps.
We apologise for any inconvenience this might have caused. If you have question or issues, feel free to contact us via our usual support channels.
Dec 4, 15:28 UTC
Mambu has identified an issue impacting deposit transaction posting with required custom fields via API v1.0. We are already working towards finding a solution as quickly as possible, but in the meantime recommend modifying the configuration of your required custom fields to not required. This will ensure your deposit transactions are posted successfully.
Please note, this issue only concerns required custom fields for transaction channels used to POST deposit transactions. Other fields or channels should not be impacted.
We are treating this with the highest priority and apologise for any inconvenience caused. If you have any questions, please don’t hesitate to contact firstname.lastname@example.org
Nov 30, 15:38 UTC