Account APIs
Create and manage resources with documented lifecycle states.
For platforms
Embed accounts, cards.
Payments and digital assets.
Use one integration layer for eligible customer accounts, safeguarded balances, partner-issued cards, transfers and conversion.
account.jsConnected
const account = await byplata.accounts.create({
type: "business",
currencies: ["EUR", "USDT"]
});
type: "business",
currencies: ["EUR", "USDT"]
});
POST/v1/accounts201
POST/v1/cards201
GET/v1/balances200
WEBHOOK DELIVEREDpayment.settled · 200 OK
BYPLATA API · SANDBOXCONNECTED
POST /accountsCreate accountCustomer resource and lifecycle stateGET /balancesRead balancesAvailable, held and pending amountsPOST /paymentsSend paymentIdempotent instruction and statusPOST /cardsIssue cardEligible programme configurationPOST /quotesRequest quoteRate, fee, expiry and proceedsWEBHOOK /eventsReceive eventsSigned lifecycle notificationsIntegration surface
One resource model is more valuable than one large API.
Platforms need predictable objects for accounts, balances, payments, cards, quotes and statements. Each resource should expose a clear lifecycle, stable identifiers and events that can be processed more than once without duplicating financial actions.
Hosted onboarding and controlled components can reduce implementation time, while APIs and webhooks connect the resulting customer activity to the platform’s own product and operations.
Responsibility model
Embedded finance still needs visible ownership.
The commercial experience may be embedded, but onboarding, safeguarding, screening, support, complaints and incident handling require an agreed division of work.
Platform responsibilities
- Present the approved customer journey and disclosures
- Protect platform credentials and user sessions
- Provide first-line context and product support
- Use events and idempotency as documented
byplata and partner responsibilities
- Operate agreed account and transaction controls
- Maintain regulated-provider integrations
- Return authoritative resource states and records
- Escalate compliance and operational exceptions
Build for operations
The integration continues after the first successful API call.
Retries, webhooks, reconciliation, support tools, role permissions and incident handling determine whether an embedded programme remains reliable at scale.
Balances and ledger
A consistent history across fiat and digital assets.
Events and reporting
Signed webhooks for account, card and settlement records.
Available resources and responsibility boundaries depend on the final programme, launch markets, licensed partners and approved customer use cases.
Embed the account lifecycle, not a collection of endpoints.
Connect onboarding, balances, payments, cards, conversion and events through one accountable integration model.