E-Wallet Acceptance
Currently Our E-Wallet Acceptance Service is Under Maintenance
Overview of E-wallet API
Brick’s E-Wallet API enables seamless integration with major e-wallet providers in Indonesia, allowing businesses to accept payments through a secure redirection flow. This provides customers with a fast and convenient checkout experience—no banking credentials or card numbers required.
The API is built for one-time payments, using a redirect-based flow with real-time status updates, callbacks, and optional error handling.
Key Features
There are two types of e-wallet payments:
- One time Payment:
- Customer authorizes each transaction individually using OTP or PIN
- Ideal for quick checkouts with minimal data collection
- No need for persistent account linking
- Redirect-based flow with real-time confirmation
- Tokenized Payment: (coming soon)
- User links their e-wallet once using PIN/OTP
- Future transactions use a stored token and may require only a PIN—or no further authentication
- Suitable for auto-debit or subscription models
Currently, Brick supports one-time payments only. Tokenized payments are not yet available.
Supported E-Wallet Channels
E-wallet Name | Bank Short Code | Max Amount | Settlement Time | Link Expiration Time |
---|---|---|---|---|
LinkAja | LINKAJA | Non-premium: 2,000,000 Premium: 10,000,000 | T+1 working day | Value is fixed to 5 minutes |
Dana (on maintenance) | DANA | Non-premium: 2,000,000 Premium: 20,000,000 | T+1 working day | Value is fixed to 60 minutes |
Premium vs Non-Premium Accounts:
Limits are based on the user's e-wallet tier. Non-premium accounts typically have lower transaction caps.
Callback Notification Flow
For every successful transaction, Brick sends a callback notification to your configured callback URL. The notification includes:
- Transaction reference
- Status (PAID, FAILED, etc.)
- Amount
- Timestamp
You can use this to:
- Mark orders as paid
- Send customer confirmation emails
- Trigger fulfillment or delivery logic
Updated 9 days ago