New app version available.
DESIGN ENVIRONMENTDesign a route ↘
CONNECT INSTITUTIONS. COORDINATE THE FLOW.
One instruction.
Across borders.
Bloch Pay is being developed as market infrastructure for payments: connecting banks, regulated entities and digital-asset providers through common instructions, partner routing and reconciliation.
The studio produces integration drafts and local event scenarios. Connections to banks, VASPs/PSAVs and settlement rails require partner onboarding and qualification; none are activated here.
01 / ORIGINBank · PSP · VASPFunding and customer relationship
→02 / BLOCH PAYCoordinate + reconcileInstructions, routing and evidence
→03 / DESTINATIONSettlement partnerRail settlement and beneficiary credit
YOUR INTEGRATION WORKSPACE
Partner directory
Save the parties you are evaluating, their declared rail coverage and internal review references. Directory entries do not assert an existing partnership or authorization. Data stays in this browser.
SAVED DRAFTS / LOCAL SCENARIOS
Your connection map
Corridor summary
Planned connectionsKeep the studio portable
Local browser data
Export a backup to retain a copy. Browser storage is not encrypted by Bloch Pay and can be cleared. Invoice backups are separate.01 / INTEGRATION ECOSYSTEM
A role for every participant
Banks & regulated PSPs
Account access, payment initiation, domestic rail connectivity, settlement reporting and beneficiary credit.
VASPs & PSAVs
Partner-operated on/off ramps, virtual-asset transfers and conversions, with identity and transfer-information responsibilities mapped per corridor.
Custodians
Safekeeping, controlled asset release and custody evidence where the selected partner model requires them.
FX & liquidity providers
Partner quotes, fees, liquidity reservations and funding. Fiat and digital-asset legs keep their own amounts and settlement records.
Platforms & operators
ERP, marketplaces, payment orchestrators and treasury teams connect business references to the underlying partner instructions.
Data & risk services
Evidence, exception review and optional Red & Blue integration. Participant authorization and transaction decisions remain with the responsible institution.
Explore BI-PoRB ↗02 / PARTNER-LED FINAL SETTLEMENT
Local rails. Connected workflows.
Settlement evidence comes from the responsible bank or provider under its rail and account arrangement. Bloch transaction finality and fiat settlement are tracked separately. Beneficiary credit and any subsequent return remain separate events.
SEPA / SCT Inst
Connect through a participating payment service provider, with scheme-specific status and settlement evidence.
EPC participation model ↗ACH
Connect through financial-institution partners. Track initiation, operator settlement and returns as distinct states.
Nacha developer guide ↗Pix
Connect through a Pix participant, with direct or indirect SPI access as applicable to the responsible institution.
BCB participant model ↗Other rails + BLCH
Describe additional domestic or bank-transfer rails. Native BLCH is a separate optional asset leg with its own evidence.
Bloch network evidence ↗03 / INTEGRATION DESIGN TOOL
Build a route draft
Use internal partner references, not account numbers or personal data. Select the roles and rails for both legs. The planner does not obtain quotes or check participant eligibility.
04 / SHARED INTEGRATION CONTRACT
Instructions in. Evidence out.
Partner adapter contract
Payment intents carry exact minor-unit amounts, source and destination currencies, participant references, and an explicit conversion quote reference when provided.
- Idempotent instruction creation
- Separate funding and payout legs
- Partner-scoped identities and permissions
- Signed event and settlement references
- Return handling and reconciliation
Qualification before connection
Each corridor needs a responsible partner and a tested operating model.
- Entity eligibility, licensing scope and rail access
- Customer identity, screening and transfer information
- FX, liquidity, fees and funding arrangements
- Custody or safeguarding responsibilities
- Authenticated adapters and replay-resistant events
- Settlement evidence, exception handling and recovery