OneBrick Payment API
✓ Official Vendor SpecPaymentsPayouts Transfersbearer14 EndpointsREST
For Agents
Disburse funds to Indonesian bank accounts, generate virtual accounts and QRIS codes, accept e-wallet payments, and validate bank accounts via the OneBrick payment platform.
Use for: I need to disburse funds to an Indonesian bank account, Validate this Indonesian bank account number before sending money, Generate a virtual account for an incoming payment, Create a dynamic QRIS code for a 50000 IDR transaction
Not supported: Does not handle accounting, KYC document review, or general-purpose card processing outside Indonesia — use for Indonesian disbursements, virtual accounts, QRIS, and e-wallet payments only.
OneBrick provides Indonesian financial infrastructure for disbursements, virtual accounts, QRIS, e-wallet payments, and bank account validation. The API issues OAuth-style access tokens, retrieves account balance, lists top-up bank options, and creates standard or BIFAST disbursements to local bank accounts. It also generates open and closed virtual accounts, dynamic QRIS codes, e-wallet payment requests, hosted checkout sessions, and B2C subaccounts for ledger isolation.
Install Jentic One Beta
Connect the OneBrick Payment API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OneBrick Payment API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with OneBrick Payment API.
Generate access tokens for authenticated payment operations
Disburse funds to Indonesian bank accounts via standard and BIFAST rails
Validate bank account ownership before triggering a disbursement
Create open and closed virtual accounts for incoming payments
Generate dynamic QRIS codes for in-person and online QR payments
Accept e-wallet payments and create hosted checkout sessions
Create B2C subaccounts to isolate balances and ledgers per end user
Use Cases
Patterns agents use OneBrick Payment API for, with concrete tasks.
★ Marketplace Payouts to Indonesian Sellers
Disburse seller earnings to local bank accounts using OneBrick's BIFAST and standard disbursement rails. POST /bifast-disbursements supports near-real-time settlement, while GET /bank-account-validation confirms ownership before transfer to reduce failed payouts. GET /disbursements/{disbursementId} returns settlement status for ledger reconciliation.
Validate bank account 1234567890 at BCA, then create a BIFAST disbursement of 250000 IDR with reference 'payout-2026-06-order-9876'.
QRIS and E-Wallet Acceptance
Accept Indonesian payments via QRIS QR codes and major e-wallets without integrating each rail individually. POST /generate-dynamic-qris returns a single-use QR string for the cart total; POST /create-payment-ewallet routes to wallets such as OVO, DANA, and ShopeePay through one endpoint.
Generate a dynamic QRIS code for an order of 75000 IDR with merchant reference 'order-12345' and a 15-minute expiry.
Virtual Account Collection
Issue per-customer virtual accounts so each incoming bank transfer is automatically reconciled to the right buyer or invoice. POST /generate-open-va creates a reusable open virtual account; POST /generate-closed-va creates a single-use account fixed to a specific amount.
Create a closed virtual account for buyer 'cust-2026-001' fixed to 199000 IDR for invoice INV-998.
Agent-Run Disbursements via Jentic
Finance agents validate accounts and trigger disbursements through Jentic without ever holding the OneBrick bearer token. The agent searches for the disbursement intent, loads the schema, and executes the call with structured parameters from upstream tooling.
Use Jentic search 'create onebrick disbursement' to locate POST /disbursements, load its schema, and execute the disbursement with verified bank details.
Key Endpoints
14 endpoints — onebrick provides indonesian financial infrastructure for disbursements, virtual accounts, qris, e-wallet payments, and bank account validation.
METHOD
PATH
DESCRIPTION
POST
/auth/token
Generate a public access token
POST
/disbursements
Create a disbursement
POST
/bifast-disbursements
Create a BIFAST disbursement
GET
/bank-account-validation
Validate an Indonesian bank account
POST
/generate-open-va
Create an open virtual account
POST
/generate-dynamic-qris
Create a dynamic QRIS code
POST
/create-payment-ewallet
Create an e-wallet payment
GET
/balance
Get the current account balance
POST
/auth/token
Generate a public access token
POST
/disbursements
Create a disbursement
POST
/bifast-disbursements
Create a BIFAST disbursement
GET
/bank-account-validation
Validate an Indonesian bank account
POST
/generate-open-va
Create an open virtual account
POST
/generate-dynamic-qris
Create a dynamic QRIS code
POST
/create-payment-ewallet
Create an e-wallet payment
GET
/balance
Get the current account balance
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
OneBrick client secrets and bearer tokens are stored encrypted in the Jentic vault (MAXsystem). Agents only ever hold a scoped reference, so production credentials never appear in prompts or logs.
Intent-based discovery
Agents search by intent (e.g. 'disburse funds to indonesian bank account') and Jentic returns the matching disbursement operation with its input schema and validation requirements.
Time to first call
Direct integration: 3-7 days to handle token rotation, callback signing, and reconciliation flows. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe API
Stripe offers global payment acceptance and payouts but lacks native Indonesian rails like QRIS and BIFAST.
Choose Stripe for global card acceptance; choose OneBrick when the use case is Indonesia-specific bank transfers or QRIS.
FAQs
Specific to using OneBrick Payment API through Jentic.
What authentication does the OneBrick Payment API use?
The API uses HTTP bearer tokens. Call POST /auth/token to mint a public access token, then send it in the Authorization header. Through Jentic the secret credentials live in the encrypted vault and the agent only handles a scoped reference.
Can I disburse funds to Indonesian bank accounts with OneBrick?
Yes. POST /disbursements creates a standard disbursement and POST /bifast-disbursements uses the BIFAST rail for near-real-time settlement. Validate the destination first with GET /bank-account-validation to reduce failed payouts.
Does the OneBrick API support QRIS payments?
Yes. POST /generate-dynamic-qris returns a single-use QR string for a specified amount. The QR can be displayed in checkout flows or printed for in-person collection.
How do I check the status of a disbursement?
GET /disbursements/{disbursementId} returns the current status of a previously submitted disbursement. Use this for reconciliation against your internal ledger or in webhook-style polling loops.
What are the rate limits for the OneBrick Payment API?
Rate limits are not declared in the OpenAPI spec. Consult onebrick.readme.io for the current sandbox and production tier limits before scaling traffic.
How do I generate an access token through Jentic?
Search Jentic for 'onebrick generate token', load the POST /auth/token schema, and execute with the client credentials stored in the Jentic vault. Subsequent operations reuse the returned bearer token automatically.
GET STARTED