Configure your integration

A Weavr integration is shaped by four decisions: your use case, the identity type of your customers, the transactions that move money, and the 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). that hold and spend it. Pick yours below - your selection is saved locally in this browser, so other pages can guide you to the right place.

1

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.

2

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.

3

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.

4

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.

Your selection

Make a selection above to see it summarised here.

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

What your selection unlocks

Your choices are saved in this browser's localStorage under weavr-integration-profile. Nothing is sent to Weavr. Other 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 and recommendations to your setup. Clear it any time with the Reset selection button.