BrickCollect · Checkout Page

A ready-made checkout page. Go live today, not next sprint.

Checkout Page is a hosted Brick payment experience — combine API-driven session creation with dashboard-managed branding. Share a checkoutUrl via web, chat, invoice, or customer support. No payment UI to build.

Brick Checkout Page experience showing checkout form, payment methods, and mobile preview

OUR SOLUTION

Brick Checkout Page: one hosted experience, two separate concerns.

Checkout Page shares separation between responsibilities. Your backend drives session creation via API. Your branding, redirect, callback, and page settings live in the Brick Dashboard — no deployment needed to update them.

Virtual Account QRIS Dynamic Payment Link
E-Wallet (GoPay, OVO, Dana) Real-time Callback Auto Reconciliation
API

Your Backend Controls

Transaction-specific session logic — handled entirely from your backend code.

  • Generate a public access token per session
  • Create a checkout session via API — receive a checkoutUrl
  • Redirect or share the checkoutUrl with your customer
  • Store the transaction referenceId for reconciliation
  • Receive payment callbacks to your configured webhook
  • Check status anytime via the Checkout Status endpoint
Dashboard

Brick Dashboard Controls

Merchant-level configuration managed from Settings › Checkout — no code changes needed.

  • Page title, primary color, font color & family
  • Logo URL and favicon
  • Success URL and Failed URL (redirect after payment)
  • Receipt delivery (email and WhatsApp)
  • Published Key for frontend initialization
  • Allowed domains for embedded checkout flows

HOW BRICK CHECKOUT PAGE WORKS

Configure once. Create sessions per transaction.

Configure in Dashboard

Set branding, redirect URLs, and receipt settings once in Settings › Checkout. These apply to every checkout session going forward.

1

Create a Session via API

Your backend generates a public access token, then calls the Create Checkout Page Session endpoint. Receive a checkoutUrl in response.

2

Share & Receive Callback

Redirect your customer to the checkoutUrl or share it via chat, invoice, or support. Brick sends a real-time callback when payment completes.

Examples of Using Brick Checkout Page

Web Commerce

Web Commerce

Redirect buyers to Brick Checkout after order confirmation. No custom payment UI — Brick handles the full selection and confirmation experience.

Chat & Messaging

Chat & Messaging

Share a checkoutUrl directly in WhatsApp, Telegram, or in-app chat. Customers pay without leaving their conversation context.

Invoice Payments

Invoice Payments

Embed or link a checkout session in digital invoices. Customers pay on their own time — Brick handles status tracking and callbacks automatically.

Customer Support

Customer Support

Support agents can generate and share a checkout link on the spot — no engineering involvement needed per transaction.

OUR SOLUTION

Two endpoints.
Complete checkout flow.

Checkout Page is powered by two endpoints. Use Create Checkout Page Session to generate each transaction's checkout URL, and Checkout Status to retrieve payment state at any time — in addition to the real-time callback.

POST

Create Checkout Page Session

Generate a new checkout session for a transaction. Returns a / checkoutUrl to redirect or share with the customer.

GET

Get Checkout Status

Retrieve the latest payment status for a checkout session. Use alongside callbacks for complete status coverage.

Configuration & Implementation Guide
Checkout Page — credential model

# Checkout Page uses different credentials

# for different layers of the integration

—— Frontend

Published Key

Loads merchant checkout config (safe for frontend)

—— Backend

Client ID + Client Secret

Used to generate a publicAccessToken

publicAccessToken

Authorizes Create Session & Checkout Status

—— Important

⚠ Never expose Client Secret in frontend code

Use redirect URLs for UX only — always rely

on callbacks for payment confirmation

✓ See full details in Configuration & Implementation

PREREQUISITES

What you need before integrating.

Ensure these are in place before calling the Checkout Page API in production.

01 /

Verified Brick Account + Active Dashboard

A completed KYB (Know Your Business) verification and an active Brick Dashboard account. Production API access is only enabled after KYB approval.

→ Configuration › Verify Your Account (KYB)
02 /

API Credentials (Sandbox or Production)

Your Client ID and Client Secret from Configuration › API Credentials. Credentials are environment-specific and cannot be mixed between sandbox and production.

→ Configuration › API Credentials
03 /

Callback URLs Configured in Dashboard

The relevant callback URLs must be set in your Brick Dashboard before going live. Payment confirmation should always rely on callbacks — not redirect URLs alone.

→ Configuration › Callback URL
04 /

Checkout Page Branding Configured

Set your page title, brand colors, logo, and redirect URLs in Settings › Checkout before creating your first session. These apply to all sessions until changed.

→ Configuration › Verify Your Account (KYB)

Settlement: Payments are settled into your Brick account balance once the settlement time has been fulfilled. Redirect URLs are for UX only — always confirm payment status via callbacks or the Checkout Status endpoint.

BENEFIT

Benefits of Using Brick Checkout Page

Ensure these are in place before calling the Checkout Page API in production.

Go Live Without Building a Payment UI

Go Live Without Building a Payment UI

No design sprint. No frontend sprint. The payment selection, confirmation, and method-handling UX is already built. Integrate one endpoint, redirect your customers, and you're live.

Branding You Control from Dashboard

Branding You Control from Dashboard

Update your page title, colors, logo, and redirect URLs at any time from Settings › Checkout — no code change or redeployment required.

Share via Any Channel

Share via Any Channel

The checkoutUrl is a standard URL — share it through web redirects, chat, WhatsApp, email invoices, or customer support flows. It works wherever a link works.

Real-Time Payment Confirmation

Real-Time Payment Confirmation

Every successful payment triggers an immediate callback to your configured webhook URL. No polling. No delays. Fulfil orders as soon as payment is confirmed.

Bank-grade Security by Default

Bank-grade Security by Default

SSL encryption, session-scoped tokens, and amount tampering protection are all built into Brick Checkout Page. Compliance without extra engineering effort on your end.

Automatic Reconciliation in Dashboard

Automatic Reconciliation in Dashboard

All Checkout Page transactions are recorded in Brick Dashboard with your referenceId. Filter, export, and reconcile without manual tracking.

Try it for free now!

Simplify your payment acceptance today. Checkout Page is available as soon as your Brick account is verified and active.

Try Brick Checkout Page for Free!