Ewallet
Brick Ewallet Payment is a Receive Money flow for collecting one-time customer payments through supported Indonesian Ewallet providers. Your system creates an Ewallet payment link, redirects the customer to the Ewallet authorization flow, and receives status updates from Brick.
Use Ewallet Payment when you need a mobile-first payment flow where customers authorize each transaction through an Ewallet app using OTP or PIN. Brick currently supports one-time Ewallet payments; tokenized Ewallet payments are not available yet.
What You Can Do With Ewallet Payment
- Create a one-time Ewallet payment link by API.
- Redirect the customer to the supported Ewallet provider.
- Track Ewallet payment status by Brick reference.
- Receive callback notifications when transaction status changes.
- Reconcile Ewallet transactions from API responses, callbacks, and dashboard records.
Payment Types
There are two types of Ewallet 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 payment flow
- Tokenized Payment: (coming soon)
- User links their Ewallet 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 Ewallet Channels
| Ewallet 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 Ewallet tier. Non-premium accounts typically have lower transaction caps.
Callback Notification Flow
For Ewallet payment status updates, 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