April 30, 2024

We’ve introduced three new reasons you can include when permanently blocking a customer:
- UNRESPONSIVE_CUSTOMER
- DORMANCY
- OTHER
Moving forward, when PERMANENT_BLOCK is used, the customer's account will be considered closed, and they can no longer process any further activity.
Applications rejected due to high risk or non-compliance will now be blocked from being resubmitted. Previously, such applications could be resubmitted but were rejected by our compliance team after review. With this change, applications that have been previously rejected will automatically be rejected without any wait.
- Resubmission is still allowed for reasons unrelated to compliance, such as incomplete applications, typos, or incorrect addresses.
- For individual customers, see Individual Customer Onboarding - Overview.
- For corporate customers, see Corporate Customer Onboarding - Overview.

We’ve released two new webhook events to help you manage cards:
- Card Details Updated: This event is triggered to notify the client or cardholder when any card details are updated. For more details, see Card Details Updated.
- Card Expiry Alert: This event is triggered when a card is approaching its expiration date. For more details, see Card Expiry Alert.