PAYBloch Inc MARKET INFRASTRUCTURE / PAYMENTS
Infrastructure for payment workflows across banks, VASPs/PSAVs, PSPs and liquidity providers. Prepare native BLCH records and design cross-border routes with partner-led settlement.
Available now: local workspace + integration studio. Bank, VASP/PSAV and settlement-rail connections are in development. No payment is sent by these tools.
AVAILABLE TO EXPLORE / INFRASTRUCTURE IN DEVELOPMENT
Practical tools today, with a partner model for cross-border payments and final settlement.
Prepare BLCH receivables and payables, track partial records and exceptions, view aging and due schedules, and export exact amounts. Install the local workspace as a PWA.
Open the workspace ↗Records stay in this browser. Payments are entered manually.Design funding, conversion and payout routes with banks, regulated providers, custodians and liquidity partners. Export integration drafts and a proposed API contract.
Design a partner route ↗Design tools; no participant connection is activated.Bloch coordinates instructions, routing and reconciliation. The responsible institution provides fiat settlement and beneficiary-credit evidence; Bloch transaction finality is tracked separately.
CURRENT STATUS / SEPTEMBER 2026
Local tools now support invoice preparation, manual reconciliation and integration planning. Managed Treasury, Pay APIs and partner connections remain under development.
Create BLCH invoices, record partial payments, inspect aging and due schedules, and export backups. Design partner routes and sample event flows in the integration studio.
LOCAL PREVIEW AVAILABLEWallet hardening, complete transaction indexing, stable status APIs, finality evidence and documented credit rules are required before a controlled pilot.
GATES OPENBanks, VASPs/PSAVs, PSPs, custodians and FX/liquidity providers have explicit integration roles. SEPA, ACH, Pix and other connections require qualified partners.
NO LIVE RAILS01 / THE PRODUCT LINES
A coordinated design for controlling value movement and explaining what happened afterward.
Organizational controls for preparing and approving native BLCH transfers. Policies sit before signing; the audit trail records who proposed, reviewed and authorized each action.
Native BLCH payment workflows for platforms and operations teams. Connect a request to the resulting transaction, track status and reconcile it against the originating business record.
02 / A SINGLE WORKFLOW
Keep operational intent, network execution and accounting evidence connected.
Bind an invoice, payout or treasury instruction to an amount, destination, reference and network identity.
Evaluate roles, recipient rules and limits before a designated device signs the transaction.
Distinguish submitted, included, confirmed and qualified-finality states rather than collapsing them into “paid.”
Match transaction outputs and status to the originating instruction; preserve exceptions and an audit export.
All four steps describe the target product workflow. They depend on a hardened wallet, complete indexing and verified status data.
03 / CONTROLS + EVIDENCE
Make decisions reviewable and payment states explicit before expanding to partner systems.
Separate preparation, approval and signing; record the rule version and decision for each transfer.
Use native wallet signing without assuming an initial Bloch Pay custody role.
Link a payment reference to transaction inputs, outputs, amounts, height, slot and a qualified status.
Compare business instructions, network records and internal books with visible exception handling.
04 / ECOSYSTEM FIT
Bloch Pay builds on existing ecosystem components and on data services still being qualified.
Public-beta native signing informs the proposed organization approval and device-signing model.
Open Postern Wallet ↗Genesis-4 transactions and public explorer records provide the network evidence behind receipts.
View the explorer ↗Complete indexing, versioned APIs and reliable events are prerequisites for managed Pay workflows.
See the data roadmap ↗05 / PARTNERSHIP DEVELOPMENT
Partner roles are product requirements, not a claim of completed agreements or enabled rails.
Define approval, invoice, payout and reconciliation needs with treasury teams, exchanges and application operators.
Target: controlled workflow pilots after technical qualification.Connect device signing, indexed transaction records and status events through documented interfaces.
Target: stable contracts and support procedures.Connect banks, regulated PSPs and VASPs/PSAVs to partner-operated on/off ramps, conversion and payment rails. Each role and settlement responsibility is defined for its corridor.
Target: partner-led research; no live rail access.The site does not name partners because no specific agreement, launch date or production integration has been verified for these product lines.
06 / DELIVERY GATES
Product stages follow the Bloch Inc portfolio and the evidence required for real value flows.
Regular checkpoints, independent node comparison and reproducible network releases.
Harden the wallet, complete indexing and document stable transaction-status APIs and events.
Test policies, invoices and reconciliation with documented credit rules, recovery and support.
Consider fiat rails and regional connections only with authorized partners, legal review and settlement controls.
The local workspace and integration planner are available. Managed payment execution, custody, fiat transfers and production rail access require partner qualification and are not enabled.
PAYMENTS THAT CAN BE EXPLAINED
Explore the network and the roadmap behind organizational Treasury and Pay workflows.