Weavr Integration for Fintech Core
Embed managed accounts and cards into your product with Weavr and Fintech Core by DashDevs. Connect onboarding to managed financial services and keep balances and card activity in step with your application.
Book a Weavr integration demoWhy Fintech Core + Weavr
Weavr provides managed accounts and cards. Fintech Core connects them to your product.
Fintech Core by DashDevs is a composable fintech infrastructure and orchestration platform. With Weavr, it handles the software connection between your application and your Weavr programme. Your team designs the journey, and Fintech Core ties each step to the right customer.
From verified customer to funded card
Weavr requires KYC for consumers and KYB for corporates before accounts and cards open. Fintech Core links that outcome to your customer record, so financial actions become available only once the customer is eligible.
A funding model you choose on purpose
A prepaid card holds its own balance. A debit card spends from a linked managed account. Weavr fixes the mode when the card is created, so we agree the model with you before building the spending screens.
Events that keep your workflows current
Weavr sends webhook events as verifications and card activity change state. Fintech Core matches each event to the right customer or card, so your support team sees the same state as the customer.
Keep your own Weavr contract
Your Weavr agreement and API credentials stay with your business. Fintech Core connects to your programme as configured, using the account and card profiles that set your limits and fees.
What the Weavr integration covers
Six capabilities scoped around your Weavr programme.
Consumer and corporate onboarding
KYC journeys for consumers and KYB journeys for corporates, with each verification decision returned to the customer record and used to decide when accounts and cards can open.
Managed accounts
Account creation for verified customers, with the available and actual balances Weavr reports and statements of settled transactions, ready to show in your product.
Virtual and physical cards
Virtual cards for online spending, with physical card upgrade and activation where your programme supports them. Each card is set up in prepaid or debit mode, as enabled for your programme.
Card lifecycle controls
Card status changes such as blocking and destroying cards, with spending controls defined in your Weavr card profiles applied to each card.
Deposits, transfers and payments
Incoming deposits and transfers between managed accounts are recorded against the right customer. Outgoing payments to external bank accounts update their status as Weavr reports each stage.
Webhook updates
Signed Weavr events for due diligence, card activity, transfers and account changes. Fintech Core verifies each signature before the event updates any record.
How a card request runs
Each step waits for Weavr's answer, from onboarding request to customer record.
- 1
Onboard
Your product starts consumer or corporate onboarding, and Fintech Core creates the matching customer in Weavr.
- 2
Verify
The customer completes KYC or KYB. The decision arrives later by webhook, moving the record from pending to approved or rejected.
- 3
Request instruments
Once the customer is eligible, Fintech Core requests the account and card in your programme and stores Weavr's identifiers.
- 4
Link the card
The card is linked to its funding source and card user. Physical cards stay inactive until that user activates them.
- 5
Track
Purchases, declines, deposits and outgoing transfers arrive as Weavr events and update card, account and payment records.
- 6
Surface the result
Balances and activity appear in your product, while rejected payments and blocked cards go to your back office.
What lands on the customer record
Five KYB statuses, plus account, card and transaction references linked to one customer.
KYB status
Consumer KYC follows the same rule. Until Weavr returns APPROVED, the consumer is unverified and Fintech Core keeps accounts and cards unavailable.
Data
Customers
Customer and card-user identifiers, the link between a corporate and its card users, and the latest KYC or KYB decision with its time.
Accounts and cards
Account and card identifiers, with available and actual balances. Card number, CVV and PIN stay out of Fintech Core and display through Weavr's secure components.
- Prepaid or debit mode
- Lifecycle state
- Spending controls applied
Transactions
Transaction references, amounts and event timestamps, recorded as each state change arrives so the history shows how a payment progressed.
What stays under your control
Fintech Core handles the integration. Your programme decisions and Weavr configuration stay with you.
Programme and access
Your Weavr agreement and API credentials, with separate sandbox and live environments, each holding its own credentials and profiles.
Customers and markets
Whether you serve consumers, corporates or both, the markets approved for your programme, and which users can hold cards or act for a corporate.
Profiles and currencies
The Weavr account and card profiles that set limits, supported countries, branding and fees, and the currencies your programme supports.
Funding model
Prepaid, debit or both, decided before cards are created, because Weavr does not allow the mode to change afterwards.
Controls and authentication
Spending rules, the fees you charge customers, step-up verification for actions such as viewing card details, and the webhook events Fintech Core receives.
Ready to connect Weavr to your product?
Tell us about your Weavr programme, target markets, customer types and required workflows. We'll walk through the integration and the configuration your product needs.
Book a Weavr integration demoNo commitment. Already running a Weavr programme? We'll show you how your setup connects to Fintech Core.