BRIAPI

Name: BRIAPI API
Brand: BRIAPI
Availability: InStock

★ Only Publicly Available OpenAPI DocumentPaymentsPayment Processingbearer, apiKey4 EndpointsREST

For Agents

Collect Indonesian rupiah payments from BRI customers via virtual accounts, top up BRIZZI prepaid cards, and tokenise direct-debit mandates. Useful for merchants, marketplaces, and fintechs serving the Indonesian market.

Quickstart

Get started with BRIAPI in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"collect a BRIVA payment in Indonesia"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with BRIAPI API.

Mint OAuth client-credential access tokens for partner authentication against BRI's gateway

Create BRIVA virtual-account numbers so customers can pay via BRI ATM, mobile, or internet banking

Top up BRIZZI prepaid cards programmatically with amounts and reference IDs supplied by the merchant

Tokenise BRI debit cards for recurring direct-debit pulls without storing PAN data

GET STARTED

Start building with BRIAPI API

Explore with Jentic

View OpenAPI Document

Use for: I need to collect a payment from an Indonesian customer who banks with BRI, Generate a BRIVA virtual account for an order worth IDR 250000, Top up a customer's BRIZZI card with a specified amount, Tokenise a BRI debit card so I can pull recurring payments

Not supported: Does not handle card acquiring, international remittance, or KYC checks — use for BRI-specific BRIVA collections, BRIZZI top-ups, and direct debit tokenisation only.

Jentic publishes the only available OpenAPI document for BRIAPI, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for BRIAPI, keeping it validated and agent-ready. BRIAPI is the partner banking API from Bank Rakyat Indonesia (BRI), one of Indonesia's largest banks. It exposes core payment rails for the Indonesian market including BRIVA virtual-account collections, BRIZZI prepaid-card top-ups, and tokenised direct debit from BRI accounts. The API uses OAuth client-credential access tokens combined with a request signature header so partners can collect, top up, and debit payments programmatically from merchant or fintech back ends.

Use Cases

Patterns agents use BRIAPI API for, with concrete tasks.

★ Marketplace Checkout in Indonesia

Indonesian marketplaces and e-commerce platforms use BRIVA virtual-account numbers as a default checkout method because most BRI customers prefer paying via ATM transfer rather than card. The BRIAPI POST /v1/briva endpoint lets a merchant generate a unique virtual account per order, capture the payment when the customer transfers funds, and reconcile against the merchant's order ID. A typical integration takes 2-3 days including signature handling and sandbox testing.

Mint an OAuth token via /oauth/client_credential/accesstoken, then call POST /v1/briva to create a virtual account for IDR 250000 with customer reference 'ORDER-12345'

BRIZZI Prepaid Card Top-Up

Transit operators, parking apps, and toll partners use the BRIZZI top-up endpoint to credit customers' BRIZZI prepaid e-money cards directly from a partner application. Each top-up call carries the card identifier and the amount in IDR; BRI processes the credit and returns a confirmation that the partner can surface to the user in real time.

Call POST /v1/brizzi/topup with the BRIZZI card number and amount IDR 100000 and confirm the response status code is success

Subscription Direct Debit from BRI Accounts

SaaS and subscription businesses tokenise BRI customer debit cards via /v1.2/directdebit/tokens so they can pull recurring payments without storing card data. Once the token is established, the merchant uses it to charge the customer at each renewal cycle. This is the closest equivalent to card-on-file behaviour for the BRI customer base, which skews heavily toward debit rather than credit.

Call POST /v1.2/directdebit/tokens with the customer card identifier and store the returned token for future debit pulls

AI Agent BRI Payment Workflow Through Jentic

An AI commerce agent uses Jentic to authenticate against BRIAPI without holding raw client credentials. The agent searches for 'collect a payment from an Indonesian customer', loads the BRIVA schema, and executes the call using a Jentic-vaulted credential. Because Jentic also handles the briSignature header generation, the agent code stays focused on business logic instead of bank-specific cryptography.

Use Jentic to search 'collect a BRIVA payment in Indonesia', load the bri.co.id operation, and execute it for IDR 50000 with a unique reference

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for briapi, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/oauth/client_credential/accesstoken

Mint an OAuth client-credential access token

POST

/v1/briva

Create a BRIVA virtual account for a payment collection

POST

/v1/brizzi/topup

Top up a BRIZZI prepaid card

POST

/v1.2/directdebit/tokens

Tokenise a BRI debit card for recurring pulls

POST

/oauth/client_credential/accesstoken

Mint an OAuth client-credential access token

POST

/v1/briva

Create a BRIVA virtual account for a payment collection

POST

/v1/brizzi/topup

Top up a BRIZZI prepaid card

POST

/v1.2/directdebit/tokens

Tokenise a BRI debit card for recurring pulls

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

BRIAPI client id, client secret, and signing key are stored encrypted in the Jentic vault. Agents receive scoped execution tokens; Jentic mints OAuth access tokens and computes the briSignature header on each call so raw credentials never enter the agent context.

Intent-based discovery

Agents search by intent such as 'collect a BRIVA payment in Indonesia' and Jentic returns the matching BRIAPI operation with its parameter schema, so the agent can call it without reading the BRI partner docs.

Time to first call

Direct BRIAPI integration: 1-2 weeks including OAuth flow, briSignature implementation, sandbox onboarding, and production certification. Through Jentic: under 1 hour — search, load schema, execute against sandbox.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

DANA

Indonesian e-wallet payment API covering wallet top-ups and merchant collections

Choose DANA when the merchant's customer base prefers e-wallet over bank transfer, or when you need wider acceptance beyond BRI account holders

Complementary

BCA

Bank Central Asia partner API for virtual accounts and transfers

Use BCA alongside BRIAPI to offer customers virtual-account payments from either of Indonesia's two largest banks

Complementary

Stripe

Global card and wallet payment processing

Use Stripe for international card payments while routing local Indonesian customers through BRIAPI for BRIVA and direct debit

FAQs

Specific to using BRIAPI API through Jentic.

Why is there no official OpenAPI spec for BRIAPI?

Bank Rakyat Indonesia does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call BRIAPI via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does BRIAPI use?

BRIAPI requires two layers: an OAuth 2.0 client-credentials access token retrieved from /oauth/client_credential/accesstoken passed as a bearer token, plus a per-request briSignature header signed with your partner secret. Jentic handles both — the client id, secret, and signing key are stored encrypted in the MAXsystem vault and Jentic computes the signature on each call.

Can I create BRIVA virtual accounts with BRIAPI?

Yes. POST /v1/briva accepts an institution code, customer code, name, amount, and expiry to create a virtual account number that the customer can pay into via any BRI channel. Use the returned VA number on your checkout confirmation page.

What are the rate limits for BRIAPI?

The OpenAPI spec does not declare explicit rate limits. BRI applies partner-tier throttling; sandbox traffic is generally limited to a few requests per second, and production limits are negotiated per partner contract. Contact your BRI partner manager for the exact ceiling on your account.

How do I top up a BRIZZI card through Jentic?

Search Jentic for 'top up a brizzi card', load the bri.co.id BRIAPI schema, and call POST /v1/brizzi/topup with the BRIZZI card number and amount in IDR. Jentic supplies the access token and signature so your agent only sets the business parameters.

Is BRIAPI free to use?

Access to the sandbox is free for registered partners. Production use is subject to BRI's partner agreement and per-transaction fees that depend on your volume tier and the product (BRIVA, BRIZZI, or direct debit). Apply for production access at https://developers.bri.co.id/.