How Weavr works

Weavr is an embedded finance toolkit. We give you regulated accounts, cards, and payments as building blocks, so you can add financial features to your app without becoming a bank yourself. If you're weighing whether to build this yourself, Why Weavr sets out what we manage on your behalf.

A solution with Weavr is built on three core concepts: customers, 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)., and Transactions. Understanding how these concepts fit together is the fastest way to understand what you're building.

The ecosystem at a glance

Programme                        (your app)
└── Customer                     (your customer, as an entity)
    ├── User                     (your customer or their team)
    └── Instruments              (your customers' financial instruments)
        ├── Account(s)
        └── Card(s)
                 ↕ Transactions  (movements of money)

---

Program

A Program is your top-level configuration on Weavr, and it represents your app. Everything you create sits beneath it. When you register as an EmbedderEmbedder A company or developer that integrates Weavr's embedded finance services into their own application to provide financial services to their end customers., you get a Program in the sandbox environment and, once approved, one in Production.

---

Customers

A customer in the Weavr platform is the verified representation of one of the people or businesses who use your financial services. Before they can hold funds or make payments, they must be onboarded as a customer on Weavr.

We have two types of customer:

Corporates

Onboard business entities and verify them with KYB, including UBO and director checks.

Onboard a corporate→

Consumers

Onboard individuals and verify them with KYC, including identity and address checks.

Onboard a consumer→

Onboarding a customer is not just a data-entry step. It triggers a due diligence process. 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. go through KYBKYB Know Your Business - the identity verification process for corporate identities. This process allows you to seamlessly and securely verify your business customer's identity. Weavr will ask users to submit the necessary information and documentation so that they can get approved by financial providers. (Know Your Business); ConsumersConsumers Individual persons who can be onboarded as identities on Weavr. Consumer identities represent individual customers and require Know Your Customer (KYC) verification. For consumers, the card owner and card assignee are typically the same person. go through KYCKYC Know Your Customer - the identity verification process for consumer identities. This process allows you to seamlessly and securely verify your user's identity. Weavr will ask users to submit the necessary information and documentation so that they can get approved by financial providers. (Know Your Customer). We manage this verification flow; you embed it into your app.

A customer that hasn't passed due diligence cannot own 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). or move money. Keep this in mind when designing your onboarding UX.

Who are your end customers?

Pick one. Most B2B integrations onboard corporates; consumer flows use KYC instead of KYB.

CorporateYour customers are businesses, onboarded via KYB.ConsumerYour customers are individuals, onboarded via KYC.

---

Users

In this guide, a user is one of your customers' end users, someone who authenticates into your app to act on a customer's behalf. This is distinct from you, the developer, who manages your Program through the Weavr dashboard.

An Authorized UserAuthorized User An individual that has been invited by the root user to manage an identity's instruments and transactions. They are not the legal owner of the identity but can be granted access to perform operations on behalf of the identity. For corporates, card assignees are created as Authorized Users. US-English variant of _Authorised User_. is an individual with their own authentication credentials who can act on a customer's behalf. Every customer has at least one Authorized UserAuthorized User An individual that has been invited by the root user to manage an identity's instruments and transactions. They are not the legal owner of the identity but can be granted access to perform operations on behalf of the identity. For corporates, card assignees are created as Authorized Users. US-English variant of _Authorised User_., and exactly one of them is the Root UserRoot user The individual who creates the identity. For corporate identities, the root user needs to be a legal representative of the corporate such as a director or a representative who has the power of attorney over the company. For consumer identities, the root user is the owner of the identity. Every identity must always have one root user..

Type of authorized userAuthorized User An individual that has been invited by the root user to manage an identity's instruments and transactions. They are not the legal owner of the identity but can be granted access to perform operations on behalf of the identity. For corporates, card assignees are created as Authorized Users. US-English variant of _Authorised User_.	Description
Root UserRoot user The individual who creates the identity. For corporate identities, the root user needs to be a legal representative of the corporate such as a director or a representative who has the power of attorney over the company. For consumer identities, the root user is the owner of the identity. Every identity must always have one root user.	The Authorized UserAuthorized User An individual that has been invited by the root user to manage an identity's instruments and transactions. They are not the legal owner of the identity but can be granted access to perform operations on behalf of the identity. For corporates, card assignees are created as Authorized Users. US-English variant of _Authorised User_. who creates the customer. Always has the Admin role with full access, and this role can't be removed. For a Corporate, this must be a legal representative: a director or someone with power of attorney. For a Consumer, this is the individual themselves.
Other authorized usersAuthorized User An individual that has been invited by the root user to manage an identity's instruments and transactions. They are not the legal owner of the identity but can be granted access to perform operations on behalf of the identity. For corporates, card assignees are created as Authorized Users. US-English variant of _Authorised User_.	Additional users invited to act on the customer's behalf. Each is assigned one or more roles that control their level of access.

We provide a set of pre-configured roles (Card Assignee, Cards Management, Funds Management, Access Management, and Admin) that can be assigned to Authorized UsersAuthorized User An individual that has been invited by the root user to manage an identity's instruments and transactions. They are not the legal owner of the identity but can be granted access to perform operations on behalf of the identity. For corporates, card assignees are created as Authorized Users. US-English variant of _Authorised User_. to enforce fine-grained, per-user permissions. Role-based access control is optional; if you prefer to manage access restrictions at your app layer, users can be granted the Admin role for unrestricted access.

Customers and your app's users

A customer in the Weavr platform is separate from the account a customer signs in to in your own app. The customer is the regulated record that holds accounts, cards, and payment permissions, and the end user authenticates against it directly - Strong Customer Authentication can't be delegated to your app. Even so, your customer should experience a single app and a single set of credentials. See Customers and your app's users for how the two relate.

---

Instruments

An InstrumentInstrument 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). is a financial product owned by a customer. We offer two types:

Managed cards

Issue virtual and physical cards in prepaid or debit mode, with spend controls and 3D Secure built in.

Cards overview→

Managed accounts

Open multi-currency accounts with dedicated IBANs to receive deposits and fund cards or payouts.

Accounts overview→

Managed account

A Managed AccountManaged Account An account held at a financial institution that can be created and managed through the Weavr platform. Each account has a balance where customers can hold funds. Optionally, an IBAN can be assigned to enable wire transfers to bank accounts outside of Weavr. is a stored-value account. It holds a balance, has its own account number and sort code (or IBANIBAN International Bank Account Number - a standardized international bank account identifier. Managed accounts can be assigned an IBAN to enable wire transfers to and from bank accounts outside of Weavr. IBANs are required for EUR accounts and enable SEPA transfers.), and can receive inbound 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).. Think of it as the funding layer, where money arrives before it moves elsewhere.

Managed card

A 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. is a card, virtual or physical, that can be used to make purchases. A card draws its balance from a funding source, typically a Managed AccountManaged Account An account held at a financial institution that can be created and managed through the Weavr platform. Each account has a balance where customers can hold funds. Optionally, an IBAN can be assigned to enable wire transfers to bank accounts outside of Weavr. belonging to the same customer.

Cards can be assigned to specific Authorized UsersAuthorized User An individual that has been invited by the root user to manage an identity's instruments and transactions. They are not the legal owner of the identity but can be granted access to perform operations on behalf of the identity. For corporates, card assignees are created as Authorized Users. US-English variant of _Authorised User_.. For example, in an expenses use case, each employee might have their own card linked to a shared corporate account.

Which instruments do you need?

Select every instrument you plan to issue. Cards can be virtual, physical, or both.

Managed accountAn IBAN-bearing account that can receive and hold funds.Virtual cardA card for online and in-app spending; PAN and CVV exposed via Secure UI.Physical cardA plastic card for in-person and ATM use.

---

Transactions

A Transaction moves funds. Every transaction involves at least one InstrumentInstrument 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)., and most involve two.

Internal transfers

Move funds between two instruments inside Weavr.

Learn more→

Send transfers

Send funds from one Weavr user to another.

Learn more→

Card payments

Spend on a managed card at a merchant.

Learn more→

Incoming wire transfers

Receive funds from an external bank into a managed account.

Learn more→

Outgoing wire transfers

Send funds from a managed account to an external bank.

Learn more→

Transactions go through multiple states as they resolve, and may not complete successfully. Your app should be designed to handle the intermediate states, not just the happy path.

Which transactions do you need?

Select every transaction type that moves money in or out of your customers' instruments.

Incoming wire transfersReceive money into managed accounts via SEPA, Faster Payments, or SWIFT.Outgoing wire transfersSend money externally to a beneficiary's bank account.SendsMove money between identities on the same programme.TransfersMove money between instruments belonging to one identity.Card purchasesCard spending at merchants, online and in-person.

---

Trusted payees

A trusted payeeTrusted Payee A trusted recipient for payments, including the business or individual's details and their bank account or instrument details. Sending to a Trusted Payee may let customers skip Strong Customer Authentication (SCA) on Outgoing Wire Transfer or Send transactions, reducing the number of approval steps required. Previously referred to as a Beneficiary. is a saved external payment destination, a bank account outside of Weavr. You register trusted payeesTrusted Payee A trusted recipient for payments, including the business or individual's details and their bank account or instrument details. Sending to a Trusted Payee may let customers skip Strong Customer Authentication (SCA) on Outgoing Wire Transfer or Send transactions, reducing the number of approval steps required. Previously referred to as a Beneficiary. against a customer so that Sends to repeat destinations don't require re-entering payment details each time. Trusted payeesTrusted Payee A trusted recipient for payments, including the business or individual's details and their bank account or instrument details. Sending to a Trusted Payee may let customers skip Strong Customer Authentication (SCA) on Outgoing Wire Transfer or Send transactions, reducing the number of approval steps required. Previously referred to as a Beneficiary. can also reduce the Strong Customer Authentication (SCASCA Strong Customer Authentication - a two-factor authentication solution required by PSD2 regulations for when end-users are accessing their payment account sensitive information or initiating transactions. SCA requires at least two of the following: something you know (password), something you have (device), or something you are (biometrics).) friction on outgoing payments.

---

Putting it together

A typical flow looks like this:

1. Your customer onboards: you create a customer and complete KYCKYC Know Your Customer - the identity verification process for consumer identities. This process allows you to seamlessly and securely verify your user's identity. Weavr will ask users to submit the necessary information and documentation so that they can get approved by financial providers. or KYBKYB Know Your Business - the identity verification process for corporate identities. This process allows you to seamlessly and securely verify your business customer's identity. Weavr will ask users to submit the necessary information and documentation so that they can get approved by financial providers..
2. The customer creates a Managed AccountManaged Account An account held at a financial institution that can be created and managed through the Weavr platform. Each account has a balance where customers can hold funds. Optionally, an IBAN can be assigned to enable wire transfers to bank accounts outside of Weavr. to hold funds.
3. Funds arrive via an Incoming Wire TransferWire 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)..
4. The customer issues a 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., funded from the account.
5. The cardholder makes Card Purchases against the card.
6. Your app reads transaction statements to display balances and history.

The primitives are intentionally composable. A corporate might have a single central account and dozens of employee cards. A consumer might have one account and one card. The model accommodates both without special-casing either.

---

Your integration profile

Pick your use case to round out the picture. Other docs pages can read this profileProfile A template defining the configuration for one type of object - corporate identity, consumer identity, managed account, managed card, transfer, or outgoing wire transfer. When you create one of these objects you reference its Profile ID, which tells Weavr which limits, currencies, supported countries, branding, and fees to apply. Your programme ships with one or more Profile IDs per supported object type. to tailor examples to your setup.

What's your use case?

Pick the option closest to what you're building. Your use case shapes which features matter first.

Spend managementCorporate cards and expense tracking for your customers' teams.Marketplace payoutsPay sellers, creators, or contractors on your platform.Accounts payableAutomate supplier and invoice payments.Embedded bankingOffer accounts and cards to your customers as part of your product.Workforce and payrollPay employees or contractors, often via cards.Exploring or something elseNot sure yet, or your use case isn't listed here.

Your selection

Make a selection above to see it summarised here.

Saved locally in this browser. Nothing is sent to Weavr.

---

What we manage vs. what you manage

We manage: identity verification, card issuing, account infrastructure, scheme connectivity, regulatory compliance, transaction processing.

You manage: your app's UX, user authentication, and how you surface financial data to your end customers. Our role-based access control handles per-user permissions, though you may also layer on additional restrictions at your app level. You also need to ensure your solution is compliant with applicable regulatory frameworks and partner compliance requirements (for example, Apple Pay). We can support you with this.

The API gives you the primitives. What you build with them is up to you.

---

Glossary

Term	Definition
Program	Your top-level configuration on Weavr, representing your app.
Customer	The verified representation of a business or individual you serve, either a corporate (business) or consumer (individual).
User / Authorized UserAuthorized User An individual that has been invited by the root user to manage an identity's instruments and transactions. They are not the legal owner of the identity but can be granted access to perform operations on behalf of the identity. For corporates, card assignees are created as Authorized Users. US-English variant of _Authorised User_.	An end user of your app who can authenticate and act under a customer. Not to be confused with you, the developer, who manages your Program through the Weavr dashboard.
InstrumentInstrument 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). / 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).	A financial product (Managed AccountManaged Account An account held at a financial institution that can be created and managed through the Weavr platform. Each account has a balance where customers can hold funds. Optionally, an IBAN can be assigned to enable wire transfers to bank accounts outside of Weavr. or 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.) owned by a customer.
Transaction / Transactions	A movement of funds involving one or more 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). (e.g. transfer, send, card purchase, wire transferWire 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).).
Trusted payeeTrusted Payee A trusted recipient for payments, including the business or individual's details and their bank account or instrument details. Sending to a Trusted Payee may let customers skip Strong Customer Authentication (SCA) on Outgoing Wire Transfer or Send transactions, reducing the number of approval steps required. Previously referred to as a Beneficiary.	A saved external payment destination (bank account outside of Weavr) registered against a customer.

---

Next steps

• 15-minute quickstart guide: get hands-on with the API
• Customers overview: learn about onboarding and due diligence
• Instruments overview: accounts and cards in depth
• Transactions overview: understand how money moves