POST /transactions
Create the escrow object from your checkout or operations flow
Initialize the amount, parties, funding rules, and release conditions from your own app instead of forcing users into a separate process.
Developers
Build escrow into your product with an API-first workflow
Trustners gives engineering teams the infrastructure to create, fund, hold, release, and monitor escrow transactions from their own application logic.
Integration model
API + webhook driven
Escrow logic
Create, fund, hold, release
Built for
Platforms and custom flows
Developer focus
Events, audit trail, control
Integration flow
Design the escrow lifecycle around your own product events
The integration model is straightforward: create the transaction from your backend, move it into a funded state, and subscribe to lifecycle changes through webhook events.
POST /transactions/:id/fund
Move the transaction into a funded and held state
Once payment is confirmed, Trustners holds the funds and exposes the current status back to your platform.
escrow.transaction.updated
Consume lifecycle events through webhooks
Listen for verification, milestone completion, approval, review, release, refund, and dispute transitions as they happen.
RequestWebhook eventObjects
Sample request
curl -X POST https://api.escrowbolt.com/v1/transactions \
-H "Authorization: Bearer sk_live_••••••••" \
-H "Content-Type: application/json" \
-d '{
"amount": 125000,
"currency": "USD",
"buyer": { "id": "buyer_2048" },
"seller": { "id": "seller_9012" },
"release_condition": "buyer_approval",
"metadata": { "order_id": "PO-1842" }
}'Sample event
{
"type": "escrow.transaction.updated",
"transaction_id": "txn_1842",
"status": "funds_held",
"release_condition": "buyer_approval",
"occurred_at": "2026-07-02T08:40:15Z"
}Core transaction object
transaction.idtransaction.statustransaction.amounttransaction.release_conditiontransaction.counterpartiesWhat you can build
The pieces teams need to embed escrow into real systems
Trustners gives engineering teams the transaction controls, status updates, and operational visibility needed for trust-sensitive payments.
Transaction orchestration
Create transactions, attach counterparties, define terms, and control approval or release conditions from your own application.
Webhook-first state changes
Receive transaction updates as events so your product can react to funding, verification, review, release, and dispute activity.
Audit-ready records
Keep a structured history of agreement changes, fund movement, evidence, and outcomes linked to each escrow transaction.
Secure integration surface
Use authenticated requests, permissioned operations, and platform-level verification before money moves through your workflow.
Integration surfaces
One escrow backend, multiple ways to connect it
Some teams need a simple transaction API. Others need webhook-driven synchronization, internal approvals, and richer transaction state in their own product. Trustners supports that model.
Transaction API
Create, fund, inspect, release, refund, and review escrow transactions from your backend.
Webhooks
Keep your product state in sync as transactions move through funding, verification, disputes, and payout.
Counterparty records
Associate buyers, sellers, vendors, or milestone participants to a transaction with clear operational context.
Operational controls
Add approval steps, review paths, and internal decision points before funds are released.
Common questions
Developer integration, explained
Answers about API control, webhook events, integration planning, and where Trustners fits into a product architecture.
Start with the transaction logic, then build the integration around it
If your product needs held funds, approval-driven release, or a dispute path tied to real transaction terms, Trustners gives your team the escrow infrastructure to build on.