Answers for every step of building with Brick

Brick is financial infrastructure for businesses that need to send money, accept payments, and manage connected financial workflows through APIs or an operational dashboard.

Related: Product overview · Explore Brick products

Brick is designed for registered businesses, platforms, marketplaces, fintech companies, and operational teams that need reliable payment capabilities embedded in their products or workflows.

Related: Contact Sales · Registration guide

No. Brick provides payment and financial-infrastructure capabilities for businesses. Brick does not offer personal loans or investment products to consumers.

Related: Fraud awareness · Legal information

Usually no for standard payment acceptance and disbursement journeys. Certain products or regulated onboarding models may require additional end-user information; the applicable flow is confirmed during onboarding.

Related: Product guide · Talk to Sales

Use the API when payments need to be embedded and automated inside your application or internal system. Use the Dashboard when operations or finance teams need to manage payments without building a direct integration.

Related: API overview · Dashboard overview

Disbursement API is intended for automated payouts triggered by your system. Non-API Disbursement supports operational and bulk payout workflows managed from the Dashboard, including file-based processing where available.

Related: Send Money · Bulk disbursement guide

Dynamic QRIS is generated for a specific payment request and can include transaction-specific information. Static QRIS can be reused and is typically suited to simpler merchant-presented payment scenarios.

Related: QRIS overview · Acceptance guide

Yes. Eligible products can be activated under the same business account so your team can manage incoming and outgoing payment workflows in one operating environment. Activation depends on KYB, product eligibility, and commercial setup.

Related: Products · Contact Sales

Brick is intended for eligible registered businesses. Availability depends on the legal entity, business activity, requested product, and the onboarding requirements applicable to that service.

Related: Registration guide · Eligibility

Typical documents may include the business registration number, corporate deeds and approvals, tax identification, and director or authorized-person identity documents. Exact requirements depend on the legal entity and product.

Related: KYB checklist · Registration guide

KYB helps Brick verify the business, its authorized representatives, ownership information, and intended use of payment services. It supports regulatory, security, and risk-management obligations.

Related: KYB guide · Privacy policy

Yes. You can use Trial Mode or the relevant test environment while verification is in progress. Production credentials and real transactions are enabled only after approval and product activation.

Related: Trial Mode · Go-live checklist

Pricing varies by product, payment channel, transaction method, committed volume, and the commercial arrangement for your account. The current quotation or service agreement is the source of truth for account-specific pricing.

Related: Pricing · Request a quotation

Billing treatment can differ by product and transaction outcome. Review the pricing terms attached to your account or contact your Brick representative before relying on a general rule.

Related: Pricing terms · Contact Finance

Setup fees, platform fees, and monthly commitments depend on the product and commercial plan selected for your business. They are confirmed during the sales and onboarding process.

Related: Pricing · Contact Sales

Yes. Businesses with larger or predictable transaction volumes can discuss account-specific commercial terms, product bundles, and invoicing arrangements with the Brick Sales team.

Related: Enterprise pricing · Contact Sales

Yes. Brick provides a test environment or Trial Mode so your team can build and validate supported flows before Production activation. Test data and credentials must not be used for live transactions.

Related: Getting started · Sandbox guide

No. Test and Production environments use separate credentials and configuration. Store them securely and make environment selection explicit in your application.

Related: Authentication · Environment configuration

Not always. Some payment and disbursement flows are asynchronous. An initial successful response may only confirm that Brick accepted the request for processing; use callbacks and the status API to confirm the final outcome.

Related: Transaction lifecycle · Callback guide

Do not assume the transaction failed and immediately submit a duplicate. Check the transaction using your unique reference and the relevant status endpoint, then retry only when the result and product rules allow it.

Related: Timeout handling · Duplicate prevention

Status names vary by product, but common lifecycle states include initiated, processing or pending, completed, failed, and expired. Your integration should map each documented state and avoid treating an intermediate status as final.

Related: Status reference · Integration guide

A transaction may remain pending while a bank, payment network, or downstream institution processes it, while a callback is being delivered, or while the transaction requires additional checks. Use the status API before retrying.

Related: Status check · Support

Check the transaction status directly, confirm that your webhook URL is reachable, and validate your signature and response handling. If the final state remains unclear, report the transaction reference and timestamps to Support.

Related: Webhook guide · Troubleshooting

Match your reference ID with the Brick transaction ID, amount, status, and timestamps using the Dashboard, API, or available reports. Your system should retain request, response, callback, and status-check records for auditability.

Related: Reconciliation guide · Transaction reports

Settlement is the process of making successfully collected funds available according to the schedule and commercial arrangement for the relevant payment channel. A successful customer payment and an available balance can occur at different times.

Related: Settlement overview · Product terms

Settlement timing varies by payment method, bank or payment network, cut-off time, working-day calendar, and your account arrangement. Use the schedule confirmed for the product instead of assuming one timing applies to every channel.

Related: Settlement schedule · Account terms

Same Day Settlement is an optional service for eligible businesses that provides access to supported collected funds on the same day rather than the standard schedule. Availability, limits, timing, and fees depend on the product and account setup.

Related: Same Day Settlement · Contact Sales

They can affect when settlement is processed. The applicable working-day rules and cut-off times differ by channel and account arrangement, so operational teams should use the published schedule for each activated product.

Related: Settlement calendar · Support

Brick applies layered security controls that can include encrypted transport, controlled access, environment separation, monitoring, and operational safeguards. Current certifications and their formal scope should be verified on Brick’s legal or security information pages.

Related: Security overview · Legal information

Store secrets only in a secure server-side secret manager, restrict access by role, separate Test and Production credentials, rotate them when required, and never expose them in browser code, chat, tickets, or public repositories.

Related: Credential security · Go-live checklist

Implement the callback-validation method documented for your product, including the required signature and timestamp checks. Configure allowlists where supported and reject callbacks that fail validation.

Related: Callback security · IP configuration

Contact Brick through the published security or support channel and provide a concise description, affected environment, timestamps, and evidence. Do not include live secrets, private keys, OTPs, or unnecessary personal data.

Related: Report security issue · Support

The Dashboard provides operational visibility and controls for activated products, including transaction review, balance and report access, configuration, and supported non-API workflows. Available menus depend on your account and user permissions.

Related: Dashboard overview · User guide

A subaccount is a separate operating or ledger context under a main business account. It can represent a client, branch, franchise, brand, or internal unit that needs its activity tracked separately.

Related: Subaccount overview · Use cases

Supported subaccount types can be configured with their own balance or ledger context, API credentials, transaction history, and callback configuration. Exact capabilities depend on the selected subaccount model and product activation.

Related: Subaccount configuration · API guide

A Full-Access subaccount is intended to operate supported services using its own configured access. A Ledger-Only subaccount is primarily used to separate and track activity without exposing the same direct service capabilities.

Related: Subaccount types · Access control

Use the official support channel listed in the Dashboard or on onebrick.io. Businesses in onboarding can also contact their assigned Brick representative for account-specific guidance.

Related: Contact Support · Contact Sales

Brick monitors services and receives urgent reports around the clock. Account-specific first-response, escalation, and resolution commitments follow the applicable service agreement or support arrangement.

Related: Support coverage · Service agreement

Include the environment, product, your reference ID, Brick transaction ID if available, amount, timestamp and timezone, endpoint or flow, HTTP response, callback evidence, and the expected versus actual result. Never send secrets or OTPs.

Related: Troubleshooting checklist · Support

Planned maintenance and material incidents are communicated through the applicable status, support, account-management, or operational channels. Keep your technical and operational contacts current so notices reach the right team.

Related: Status updates · Maintain contacts

BrickI is Brick’s AI-powered integration and support assistant. It can help explain products and documentation, guide troubleshooting, and support approved read-only inquiries such as transaction-status or historical-analysis questions.

Related: BrickI overview · Ask BrickI

No. BrickI is designed as a read-only assistance layer and must not modify credentials, provider routing, user permissions, account settings, or transaction outcomes.

Related: BrickI security model · Access policy

Availability can depend on your account, onboarding status, product configuration, and supported communication channel. Contact your Brick representative or Support to confirm access.

Related: Activate BrickI · Support

Brick MCP provides structured Brick API context to compatible AI coding tools. It does not execute transactions, access your Brick account or transaction data, or autonomously modify your codebase; generated implementation still requires engineering review and Sandbox testing.

Related: Brick MCP · Developer documentation

No legitimate Brick representative should ask you to disclose a personal password, private key, full API secret, or OTP. Stop the conversation and report the request through an official Brick channel.

Related: Report suspected fraud · Security

No. Offers of personal loans, investment returns, account trading, or similar consumer schemes presented in Brick’s name should be treated as suspected fraud.

Related: Fraud warning · Legal information

Check the sender domain carefully, verify unexpected requests through a known Brick contact or the official website, and avoid using phone numbers or links supplied only inside the suspicious message.

Related: Official channels · Contact Support

Do not transfer funds based only on an unsolicited request. Verify the instruction through your authenticated Dashboard, contract, invoice, or a known Brick representative, then report suspicious activity to Support.

Related: Report fraud · Billing verification