Version 3.60.0
Simulating card expiration scenarios on the embedder portal
We are pleased to announce new tools to help you understand and test the card renewal process in our sandbox environment.
To keep you informed about important card lifecycle events, Weavr will send Card Notifications regarding upcoming card renewals and expired cards, allowing you and your users to take timely action. You can find more details about card renewals here
To streamline your testing and integration, we've introduced two new simulators in our sandbox embedder portal:
Card expired: This simulator instantly triggers the expiry of a selected card.
Card about to expire: This simulator initiates the card renewal process by setting the expiration date of a physical card to 60 days from the current date and a virtual card to 30 days from the current date.
Additionally, we've implemented automatic updates to card expiration dates specifically within these simulator paths, making testing even easier.
How the Simulators Work:
/cards/{card_id}/about_to_expire
Virtual Cards: The expiration date will be set to the last day of the month that is 30 days from today.
Physical Cards: The expiration date will be set to the last day of the month that is 60 days from today.
/cards/{card_id}/expire
The card's expiration date will be set to the last day of the previous month relative to the current date.
These new simulators provide a convenient and efficient way to test your integration with our card renewal notifications. We encourage you to explore these features in the sandbox environment.
Bulk Process Improvements
We've enhanced our Bulk Process functionality, providing you with greater visibility into its execution and the operations within.
The GET /bulks/{bulk_id} endpoint response now includes an operationStatusCounts field, detailing the number of operations in each status (SUBMITTED, RUNNING, COMPLETED, FAILED, CANCELLED). You'll also find the bulk process's start and finish timestamps, and the execution mode.
To keep you updated, you can now request webhook notifications on the bulk process's progress, with a frequency of up to four updates per bulk process.
Please note that in a future update, the bulk_process_end webhook will be renamed to bulk_process_progress to better reflect its function and will include the operationStatusCounts mentioned above.
API details
Webhook details
For more information, refer to the Bulk Process
Confirm passcode UI component
We’ve added a confirm passcode component to our UI library. When used in conjunction with the passcode component, it will validate that both passcodes that are entered, match.