Product orientation
Understand which Brick product and implementation path matches the payment flow your platform needs.
Brick Documentation · Integration Guides
Understand the payment flow before you build it.
Follow a structured path from product selection and account preparation to Sandbox validation and production readiness.
A clear route from idea to operation.
Use the guides in sequence or enter at the section that matches your current integration stage.
✓
Understand the product
Map your business outcome to the relevant Brick payment flow.
✓
Prepare the integration
Set up access, environments, credentials, and callbacks.
✓
Test and operate
Validate status handling, retries, and reconciliation in Sandbox.
Documentation map
Introduction
├─ What is Brick?
├─ Security at Brick
└─ FAQ
Getting started
├─ Dashboard & account
├─ API setup & environments
└─ Production checklist
Product guides
├─ Send Money
└─ Receive MoneyRecommended journey
Read in the same order your integration matures.
The documentation connects product decisions, technical setup, payment behavior, and operational readiness without mixing them into a single reference page.
01/ Choose the right path
Start with the business flow you need to support.
Use the product guides to distinguish send money, receive money, Dashboard, and supporting operational workflows before selecting an API path.
02/ Prepare safely
Prepare the account, environment, and security controls.
Review account verification, Dashboard configuration, credentials, base URLs, callback setup, and the separation between Sandbox and Production.
03/ Operate reliably
Build for asynchronous payment behavior.
Follow the documented patterns for unique references, callbacks, status checks, idempotent updates, retries, and reconciliation instead of relying only on the first API response.
04/ Review before launch
Validate readiness before using Production.
Complete Sandbox testing and review production-readiness guidance for status handling, logging, monitoring, reconciliation, and escalation paths.
Documentation coverage
Guidance for decisions, setup, and operation.
Use the documentation when you need context and recommended workflows rather than a field-by-field endpoint contract.
Dashboard & account
Prepare account verification, access, configuration, roles, subaccounts, balances, and transaction operations.
API setup
Configure credentials, environments, callbacks, authentication, and the tools used during integration testing.
Send money guides
Plan disbursement workflows, destination options, testing, status handling, transfer proof, and operational follow-up.
Receive money guides
Navigate Virtual Account, QRIS, e-wallet, and hosted Checkout Page implementation paths.
Reliability & support
Use error-handling, FAQ, security, production checklist, and troubleshooting guidance during implementation and operation.
Choose the right developer surface
Guidance first. Exact contracts when you code.
Brick separates explanatory documentation from endpoint references and AI-assisted context so each surface stays focused.
Documentation
Use for product concepts, setup sequences, security guidance, testing, and production readiness.
API References
Use while implementing requests, headers, parameters, responses, callbacks, and status endpoints.
Brick MCP
Use when a compatible AI coding assistant needs structured Brick documentation context during development.
Find the right Brick integration path.
Start with the product and setup guides, then move to the exact API contract when your implementation is ready.