Skip to main content

Multi API updates

· 3 min read

Low balance webhook, Data Insights enhancements, and breaking-change reminders​

Low balance webhook notification​

We can now send a webhook notification when the balance of an account drops below a configured threshold. This lets you react proactively—for example by automatically initiating a top-up—before transactions start failing due to insufficient funds.

A single webhook fires when the balance crosses the threshold; further transactions while still below the threshold do not trigger additional webhooks. The notification becomes eligible to fire again only after the balance has recovered to or beyond the threshold.

Thresholds are configured per currency, so you can set independent values for EUR, GBP, and any other currencies your programmeProgramme A programme represents your application within Weavr. Everything you create — Identities, Instruments, Transactions — sits beneath a Programme. When you register as an Embedder, you receive a Programme in the Sandbox and, once approved, one in Production. supports. The feature is available on request—contact our support team with the currency and threshold amount you need.

For full details, see the low balance notifications documentation and the webhook payload reference.

Fund movements dashboard on Data Insights​

A new Fund movements dashboard is available in Data Insights. It presents a clear view of your programmeProgramme A programme represents your application within Weavr. Everything you create — Identities, Instruments, Transactions — sits beneath a Programme. When you register as an Embedder, you receive a Programme in the Sandbox and, once approved, one in Production.'s financial activity for a given period, broken down into:

  • Inflows—funds received successfully into instrumentsInstrument A financial product owned by an Identity. There are two types: Managed Accounts (stored-value accounts that hold balances and can receive wire transfers) and Managed Cards (prepaid cards — virtual or physical — used for purchases).
  • Outflows—funds successfully leaving instrumentsInstrument A financial product owned by an Identity. There are two types: Managed Accounts (stored-value accounts that hold balances and can receive wire transfers) and Managed Cards (prepaid cards — virtual or physical — used for purchases).
  • End-of-month balance—to support period-end reporting

Data can be filtered by identity and time range, so you can focus on the view most relevant to your needs.

User roles visible in the CorporatesCorporates Business entities that can be onboarded as identities on Weavr. Corporate identities represent companies and require Know Your Business (KYB) verification. They can have multiple authorised users and issue cards to card assignees. dashboard​

Following the release of user roles in March, the Data Insights CorporatesCorporates Business entities that can be onboarded as identities on Weavr. Corporate identities represent companies and require Know Your Business (KYB) verification. They can have multiple authorised users and issue cards to card assignees. dashboard now surfaces role assignments. Roles appear as a comma-separated list per user in the Corporate Users table, giving you a consolidated view of access levels across your user base.

Enhanced card-level filtering in Data Insights​

To improve card-level visibility and simplify how activity is traced back to individual cards, we have added new filters and columns across several Data Insights dashboards:

  • Card Friendly Name and Managed Card ID are now available as filters in the Authorisations, Settlements, 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., and Physical CardsPhysical Card A payment card that is printed or embedded in wearables and sent to customers directly. Physical cards are created by first creating a virtual card and then upgrading it to a physical card. They are sent in an inactive state and must be activated by the card assignee before first use. dashboards.
  • Card Friendly Name is now also a column in the Details table of all dashboards.

This makes the dashboards better suited to day-to-day operational queries and investigations.

Mobile SDK improvements​

This release ships alongside several mobile SDK updates:

  • Biometric enrollment improvements—more granular failure responses, an inactivity timeout during enrollment, and clearer error messages when a session is interrupted. See: React Native v5.3.0, iOS v3.4.0, and Android v3.9.0.
  • Step-up authentication reliability—clearer failure messages when SDK configuration or Play Integrity checks are still being prepared. See: React Native v5.3.1, Android v3.10.0.

Upcoming breaking changes​

Two breaking changes announced in our March 2026 release require integration work before the production deadline of October 31, 2026:

  • Verification of PayeeVerification of Payee The EU equivalent of Confirmation of Payee (CoP). A service that validates the name of a payment beneficiary against the IBAN registered with their bank or Payment Service Provider (PSP) before a SEPA payment is executed. for EUR Outgoing Wire TransfersWire Transfer A transaction that moves funds between accounts. An incoming wire transfer moves funds from a third-party bank account to a Weavr managed account, while an outgoing wire transfer moves funds from a Weavr managed account to a third-party bank account. Wire transfers require the managed account to have an assigned IBAN (for EUR) or sort code and account number (for GBP).—mandated by the EU Instant Payments Regulation (IPR). Applies to programmesProgramme A programme represents your application within Weavr. Everything you create — Identities, Instruments, Transactions — sits beneath a Programme. When you register as an Embedder, you receive a Programme in the Sandbox and, once approved, one in Production. with OWTsOWT Outgoing Wire Transfer - a transaction that moves funds from a Weavr managed account to a bank account held at a third-party financial institution. OWTs require the managed account to have an assigned IBAN and the user to complete Strong Customer Authentication. in EUR. See the VoP overview and the create and execute guide.
  • Linked Card UsersCard User The person that a card is assigned to and who will use the card for purchases. Weavr does not support anonymous cards, and therefore all cards must be linked to a card user before a card can be used. For consumers, the card owner and the card user is typically the same person. For corporates, the card users are employees or individuals authorised to spend the corporate's funds.—every active 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. must be linked to a user with complete mandatory data and 3DS3DS 3-D Secure - an additional security layer for online credit and debit card transactions. It adds an authentication step where the cardholder verifies their identity with the card issuer during the purchase, reducing fraud and providing liability protection for merchants. enrollment. Applies to programmesProgramme A programme represents your application within Weavr. Everything you create — Identities, Instruments, Transactions — sits beneath a Programme. When you register as an Embedder, you receive a Programme in the Sandbox and, once approved, one in Production. that issue cards. See the virtual cards documentation.

To enable either feature on your sandbox account, contact our support team.