Named
Account team
Enterprise · named accounts · licensed partners
Institutional treasury,
white-glove delivery.
Named-account infrastructure for finance teams running real treasury at institutional scale. Licensed-partner routing, multi-entity intercompany flows, a dedicated CSM and white-glove onboarding — backed by the same rail.
Named accountsWhite-glove onboardingDedicated CSMLicensed partners
Regulatory status
BINK is not yet licensed in this region. Regulated services will be provided through licensed partners.
Licensed partners
Regulated services will be provided through licensed partners. No partner rails are live yet.
Enterprise engagement
What an engagement includes.
Guided
Production onboarding
Published
Live service status
Preparing
UK e-money registration
Who runs Enterprise
Four institutional segments.
Funded startups
$5M+ AUM treasury, multi-currency revenue, scaling team — Scale ceiling reached.
Mid-market finance
Multi-entity holding, intercompany flows, custom approval workflows, regulator engagement.
Family offices
Wealth ops, full audit trail, conservative risk posture.
Regulated platforms
Embedded finance: marketplaces, lenders, neobanks — operating their own end-customer surface on BINK rails.
What's included
Eight institutional capabilities.
E01
Multi-entity treasury
Holding-company structure with sub-account isolation, intercompany sweeps and consolidated reporting across regulated entities and jurisdictions.
E02
Licensed partners
Regulated services will be provided through licensed partners. When live, customer funds will be held in segregated accounts at licensed partners.
E03
Service health, published
Live service health is read from the API’s own health checks and shown on the status page. BINK does not publish latency, uptime or recovery figures.
E04
White-glove onboarding
Dedicated implementation engineer + named CSM + executive sponsor at BINK from kick-off.
E05
Approval workflows
Multi-party approvals above policy thresholds. Role-scoped keys. Hardware-bound admin. Audit log API integrated into your SIEM.
E06
Audit trail
Every action written to BINK’s internal audit log. Audit log API integrated into your SIEM. No external certifications yet.
E07
Built for regulation
BINK is not yet licensed. Preparing for UK e-money registration. Regulated services will be provided through licensed partners.
E08
Custom rails
Request a corridor or currency pair that’s not in the public catalog. Reviewed case-by-case.
Is Enterprise right for you?
Eight reliable triggers.
Any one of these means a named-account engagement makes more sense than continuing on Scale. Most enterprise buyers match three or more.
- Monthly transfer volume > $500k
- Treasury AUM > $5M
- Multi-entity / intercompany structure
- Partner-bank routing requirement
- Service-level terms in your procurement contract
- Regulator engagement requirements
- Embedded-finance / BaaS use case
- Custom currency or corridor not in catalog
Onboarding path · step by step
From architect call to production.
Architect call first, then KYB intake, partner scoping, a compliance walkthrough and production access — each step agreed with you. Production depends on licensed-partner availability in your jurisdictions. White-glove from kick-off to go-live.
STEP 01
Architect call + scoping
Treasury volumes, regulator footprint, integration target. Leave the call with a proposed engagement plan.
STEP 02
KYB intake
Corporate registry + UBO documents. Sanctions screening starts at intake.
STEP 03
Sandbox keys + architecture review
Engineer on your side. Sandbox provisioned. Webhook endpoints + idempotency primitives walked through.
STEP 04
Partner routing scoped
Regulated services will be provided through licensed partners, scoped to your jurisdictions.
STEP 05
Compliance + AML walkthrough
Compliance controls walked through. Audit log API + export walkthrough.
STEP 06
Production keys issued
Signed agreement countersigned. Production access enabled. Sandbox parity verified.
STEP 07
First production transfer · monitored
Engineer present. CSM on Slack. End-to-end monitored and reconciled.
STEP 08
Go-live + CSM handoff
Named CSM takes over. Quarterly business review cadence scheduled. Architect stays available after go-live.
Service levels · what we publish
No figure we have not measured.
BINK does not yet publish latency, settlement, uptime or recovery figures, and offers no contractual SLA today. What is published: live service health on the status page, and a signature on every webhook.
| Metric | Scale | Enterprise | Measurement |
|---|---|---|---|
| Service status | Published | Published | On the status page |
| Webhook delivery | Signed | Signed | HMAC-SHA256 on every event |
| API latency | Not published | Not published | No measurement published yet |
| Settlement time | Not published | Not published | No measurement published yet |
| Recovery objectives (RTO / RPO) | Not published | Not published | No measurement published yet |
Figures will be published here only once they are measured.
Support matrix
Four channels. One named team.
Direct line
Response
By arrangement
Hours
Agreed at onboarding
Dedicated to your account
Slack channel
Response
By arrangement
Hours
Named escalation
CSM + engineer + architect
Email · priority
Response
By arrangement
Hours
Business hours
CSM + engineering manager
Architect call
Response
By appointment
Hours
Business hours
Dedicated banking architect
Treasury migration · parallel compliance
Switch rails without breaking your books.
Migration runs in parallel to compliance onboarding. Existing treasury continues uninterrupted on your incumbent rail while we wire BINK in the background, then cut over on a controlled date.
Treasury migration
- 1Reconcile incumbent · 30-day windowOutstanding settlements paid through · books reconciled to BINK opening balance.
- 2Parallel run · 14 daysBINK receives + reports in parallel. No funds move yet. Daily reconciliation comparison.
- 3Gradual cut-over · 7 daysPer-counterparty cutover starting with lowest-risk. Each milestone signed off.
- 4Partner handover · 1 dayFinal balance lift to the licensed partner. Incumbent decommissioned.
- 5Post-migration audit · 30 daysBINK + your audit team verify reconciliation drift = 0. Migration sign-off recorded.
Compliance onboarding
- 1KYB intake · documents + UBOsCorporate registry, beneficial owners, sanctions screening. Aligned to FATF + region-specific framework.
- 2Partner scope · per jurisdictionRegulated services will be provided through licensed partners, scoped per jurisdiction.
- 3Audit log packagingInternal audit log exports scoped to your entity. No external certifications yet.
- 4Regulatory status reviewBINK is not yet licensed. We walk through what this means for your jurisdictions of operation.
- 5Audit log API + SIEM wiringAudit trail API scoped + sample exports validated. SIEM ingestion verified.
White-glove engagement
Talk to a banking architect.
30-minute call. Walk us through your treasury, transfer volumes, regulator footprint and integration target. You leave with a named engagement proposal and a go-live plan.