Order acceptance is one observation.
A timeout requires reconciliation against the same business reference. A duplicate response does not establish that the recovered order has the right side, amount, rate or funding path.
LIQUIDITY ADAPTER LAB / BRL ↔ USDT
Prepare liquidity.
Inspect every leg.
Explore conversion, funding, order recovery and treasury controls in a local test environment. Follow the exact amount from intent to the evidence needed for settlement.
CONTRACT COVERAGE11
operations mapped in private adapter tests
6 / USDT decimals2 / BRL decimals5s / quote window
Synthetic data. Local calculations. No partner connection, API key, payment instruction or transaction execution is available in this laboratory.
01 / SCENARIO LABORATORY
Test the happy path.
Exercise the failure paths.
Change the flow, amount or failure scenario. Results describe the model’s decision; they never change invoices or saved routes.
Preparing the local example…
SYNTHETIC RESULT / EXECUTION DISABLED
Source quantityUSDT · 6 decimals
Illustrative rateBRL per USDT · 4 decimals
Calculated notionalBRL · truncated to 2 decimals
Fees are not supplied. A calculated notional does not confirm quote acceptance or the provider’s limits.
Settlement evidence stays separate.
Partner orderSYNTHETIC
Fiat fundingNOT INDEPENDENTLY OBSERVED
Asset deliveryNOT INDEPENDENTLY OBSERVED
Beneficiary creditNOT OBSERVED
Inspect the normalized test result
REGRESSION EXPLORER
Three flows. Twelve scenarios.
Run all combinations using the current amount and quote age. A held case is an intentional control outcome, not a failed software test.
| Scenario | Pix-funded buy | Balance-funded buy | Sell-side review |
|---|
02 / INTEGRATION PATHS
One adapter.
Distinct responsibilities.
Start with conversion and treasury observations. Qualify each funding, custody and settlement responsibility before enabling a live route.
03 / INSTITUTIONAL ARCHITECTURE
Keep decisions traceable
across each system.
The public laboratory exercises pure controls. A future institutional deployment adds authenticated services, durable records and independent settlement evidence.
- 01Bloch Pay
Intent, approval envelope and participant scope.
- 02Server adapter
Secrets, quote deadline, request journal and recovery.
- 03Liquidity & settlement
Reported order, funding, custody and delivery.
- 04Reconciliation
Independent observations, books and exceptions.
Withdrawal recovery needs its own contract.
Available custody must be explicitly defined. An uncertain withdrawal creation stays under review until the outcome can be established without issuing a duplicate request.
Source completeness matters.
A page of order history is not a complete treasury snapshot. Preserve pagination coverage, timestamps, identifiers and missing fields before building accounting exports.
04 / OPERATING CAPACITY
Budget requests
across the whole account.
A polling illustration with 40 requests per minute allocated to order reads and 20 reserved for other operations. Production scheduling requires a shared limiter.
Read, back off, reconcile.
Polling shares the request budget with quotes, recovery and other reads. Daily trading caps require a different response from short request-rate limits. Changing API keys is not a capacity strategy.
There is no documented webhook receiver in this adapter contract. Signed downstream events would be a separate Bloch service to implement and qualify.
05 / QUALIFICATION GATES
From contract tests
to a controlled pilot.
These gates describe the remaining institutional work. Passing a synthetic scenario does not grant account access or establish a partnership.