See the real stack behind every stablecoin provider.
Review a provider’s legal entity, licenses, and banking, custody, and screening partners before you integrate.
Candidates: JPM Coin by Kinexys, a USD deposit token on Base, and Citi Token Services for Cash in New York, London, and Singapore branches. A dated FAQ names Citibank N.A. branches; the J.P. Morgan contracting legal entity and regulator register links are pending confirmation. Dependencies include approved counterparty onboarding, branch accounts, cash conversion, and settlement finality. Needs review: confirm the contracting entity, market eligibility, and account terms before selecting a rail.
Know the provider behind the pitch.
Why StablecoinRoadmapReview the contracting entity, asset, licenses, and upstream partners before you commit.
Verify the entity and asset
Check the contracting entity, license coverage, and asset issuance on your target network.
Entity & asset
- Regulated legal entity
- Issuance & redemption terms
- Covered markets & licenses
Trace hidden dependencies
Identify sponsor banks, custodians, compliance vendors, and bridges shared by providers.
Supplier graph
- Sponsor banks & custody
- Screening & travel-rule partners
- Shared upstream dependencies
Record your decision
Record your choice, alternatives, and sources, then apply policy gates at runtime.
Selection to runtime
- Dated regulator & issuer sources
- Open diligence questions
- Pre-execution compliance gates
Decide your role before you launch.
For community and regional banksAssess your bank's role, third-party risks, and whether an existing payment rail meets your needs.
Choose your role
Issuing, holding reserves, tokenizing deposits, and offering another issuer's coin carry different liabilities, deposit-insurance treatment, and provider needs.
Role & liability
- Whose liability, on whose books
- Deposit-insurance treatment
- Provider stack for that role
Review your exit options
Assess subcontractor reliance, alternative providers, and evidence gaps for each offering.
Third-party risk
- Subcontractor reliance
- Single-provider concentration
- Alternates that pass your policy
Consider existing rails
A review may find that FedNow, RTP, or a wire meets the need—or that the bank should wait. We do not issue tokens, hold reserves, or move funds.
Independent review
- FedNow, RTP & wire baseline
- Build, partner, or wait
- No token or custody to sell
Start from your industry.
IndustriesExplore published use cases, required provider services, and current platform support.
Banks & credit unions
Remittance companies
Neobanks
Merchants & marketplaces
Exchanges & on-ramps
AI agents & APIs
From corridor requirements to provider selection.
How it worksDefine your payment corridor
Set the sender, recipient, currencies, settlement asset, and jurisdictions.
Compare providers and dependencies
Compare legal entities, regulatory coverage, banking and custody partners, and evidence gaps.
Record and gate the decision
Share a source-backed selection record and apply policy gates to API keys and connected adapters.
We are not a bank, custodian, or settlement rail. We do not hold funds or issue tokens. Payment execution is simulated today.
What are you evaluating?
Where teams startScope a payment corridor
Map issuers, on/off-ramps, custody, and screening for a specific route.
Start with the corridor
- Sender & beneficiary jurisdictions
- Fiat leg & settlement instrument
- Required license classes
Review a provider
Check the contracting entity, supervising authorities, and sub-processors.
Verify the offering
- Entity & regulator register links
- Upstream bank & bridge dependencies
- Dated evidence & open gaps
Gate agent and operator workflows
Apply compliance checks, role-weighted approvals, and scoped keys before moving beyond simulation.
Control the runtime
- Resource-scoped bearer keys
- Pre-execution policy gates
- Append-only audit records
Our cloud. Your cloud. Your premises.
Deployment choicesUse our hosted platform or discuss deployment in your environment.
Hosted SaaS
Use StablecoinRoadmap.com with infrastructure managed by our team.
Default path · managed by us
- Hosted platform access by request
- Infrastructure managed by our team
- Start with a walkthrough
Your cloud
Scope deployment in your Google Cloud environment, including VPC networking, ingress and egress, and data isolation.
Scoped deployment engagement
- Google Cloud as the starting target
- Your network and data isolation requirements
- Services and responsibilities agreed together
On-premises & air-gapped
Discuss an on-premises deployment and assess which capabilities could run without external services.
Subject to feasibility and scope
- Docker packaging scoped to your needs
- Local service and integration planning
- Offline capability assessment
Customer-cloud and on-premises deployments are scoped engagements, not self-service packages. Full-platform packaging and fully air-gapped operation are not available today. Authentication, data, AI, and provider integrations must be reviewed for each environment; some features require external connectivity or alternatives.
Review providers for your corridor.
WalkthroughBring your jurisdictions, settlement asset, and candidates. We will review coverage, dependencies, and evidence gaps.