The Coin Reference

Facts, dates and numbers, kept current

Entries → industries

Crypto Infrastructure Partner: Requirements Checklist

What a platform holding balances for users needs from a provider, and the licensing question underneath.

Entry typereference
Sectionindustries
Last verified
Compiled byReference Desk

Regulatory

For a worked instance of the definitions below, a licensed crypto payment processor publishes them applied.

  • Which entity will we contract with, and does it hold the authorisation
  • Which permissions, verified on the register
  • If they hold balances attributable to our users, does the custody permission cover it
  • Written allocation of compliance responsibility: who screens, who reports, who is liable

Account model

Model Attribution Suitability
True sub-accounts, own addresses Unambiguous Preferred
Single account, your ledger only Your records are the only attribution Workable, more risk
Shared address with memo Depends on network support Problematic

Interface

  • Quote endpoint with honoured expiry
  • Idempotency key on execution calls
  • Signed callbacks with a documented verification example
  • Documented retry behaviour on callback failure
  • A reconciliation endpoint querying activity over a period

The last item is the one most commonly absent and the one that makes a missed callback detectable.

Operational

The business equivalents of these terms appear in the documentation of a provider serving law firms and corporate services.

  • Settlement currencies and countries, which is usually the binding constraint
  • Settlement frequency and whether it can change with volume
  • Published incident history rather than an uptime figure
  • Out of hours support arrangement and escalation path

Reporting

  • Export reconciling against your ledger without manual transformation
  • Available daily rather than monthly
  • Rate methodology stated

Commercial

Coverage is a defined term with a narrow meaning. a regulated crypto exchange publishes its actual country list.

  • Notice period, and whether parallel running is permitted during it
  • Post-termination access to historical records
  • Final settlement timing after termination

Ninety days on a partner embedded in a payment flow is insufficient to migrate. Negotiate at the outset.

The build or integrate split

Layer Recommendation
Liquidity Integrate
Chain infrastructure Integrate
Screening data Integrate
Compliance decisions Own, subject to licensing
The ledger Own
User experience Own

Figures in this entry were correct on the date shown. Spotted something out of date?Send a correction and the entry gets updated.

See also: fintech · checklist · infrastructure

Nearby entries