Multi API v3.21.0
Card Purchase - Decline Reasons Additional Detail
Transaction data available within the MultiMulti Weavr Multi is an embedded finance solution that allows you to integrate financial services into your own application, providing a seamless experience for your customers. It enables you to offer managed accounts, managed cards, and transactions without requiring financial expertise. Portal and the Managed CardManaged Card A payment card (virtual or physical) that can be created and managed through the Weavr platform. Cards can operate in prepaid mode (with their own balance) or debit mode (linked to a managed account). All cards must be assigned to a card assignee who is an Authorised User. Statement (GET) have been expanded. Card purchase transactions will now include decline reasons and spend rule failure reasons.
This update provides data consistency across all three sources: Portal, MultiMulti Weavr Multi is an embedded finance solution that allows you to integrate financial services into your own application, providing a seamless experience for your customers. It enables you to offer managed accounts, managed cards, and transactions without requiring financial expertise. API & webhooks. ( spendRuleFailedReason is displayed as authRuleFailedReason within webhooks)
Affected APIs:
GET managed_cards/\{id\}/statement
NameOnCard - Regex Alignment
We have consolidated the supported characters for use within the NameOnCard field of Managed CardsManaged Card A payment card (virtual or physical) that can be created and managed through the Weavr platform. Cards can operate in prepaid mode (with their own balance) or debit mode (linked to a managed account). All cards must be assigned to a card assignee who is an Authorised User..
Full regex list can be found HERE
SMS - Additional Validation Response
An additional validation response will be introduced in connection with mobile SMS verification.
409 (conflict) - “MOBILE_COUNTRY_NOT_SUPPORTED” will be returned if the country is not supported for delivery of an SMS code.
Affected APIs:
- POST /consumer
- POST /corporate
- PATCH /consumer
- PATCH /corporate
SMS - Mobile Number - Update Limit
A limit will be introduced on the number of times a consumer user can update their mobile number within a calendar year.
It will be possible to update a consumer users mobile number up to three times per calendar year. Requests beyond this will receive the below validation response:
409 (conflict) - “MOBILE_NO_CHANGE_LIMIT_EXCEEDED”
Affected APIs:
- PATCH /consumer