E-Wallet

Integration guide for the Manjo Gate E-Wallet module. With this module, merchants can accept payments from digital wallets (DANA, OVO, LinkAja, ShopeePay, Astrapay) and receive payment status notifications asynchronously.


Overview

E-wallet transactions are created through the unified transaction/create endpoint with method: 2. Gate registers the payment with the payment network, then returns a payment_url — the channel's checkout page — where the customer is redirected to pay. Once the payment is complete, Gate sends an HTTP POST to your callback_url.

Authentication

Use an API Key on every server-to-server request.

Header Value Required Description
X-API-KEY <your_api_key> Yes API Key issued by Manjo
Content-Type application/json Yes Request payload format
X-API-KEY: <your_api_key>
Content-Type: application/json

Endpoints

Page Path Purpose
Create Transaction POST /api/v1/transaction/create Create an e-wallet payment and get a payment_url.
Channel List GET /api/v1/ewallet/channel-list List of available channels (digital wallet brands).
Payment Callback POST {your_callback_url} Real-time notification from Gate after the payment completes.

Payment Workflow

  1. Select a channel: Get the channel_code from the Channel List.
  2. Create the transaction: Your backend sends POST /api/v1/transaction/create with method: 2.
  3. Redirect the customer: Take the payment_url from the response and redirect the customer to that page.
  4. Customer pays: The customer completes the payment in the e-wallet app / page.
  5. Redirect back: After completion, the customer is returned to your redirect_url.
  6. Webhook: Gate sends a notification to your callback_url.
  7. Fulfill the order: Your server verifies the trx_id and fulfills the order.

Notes

  • Payment Method Enum: method: 2 is E-Wallet.
  • Channel: channel is required and must exist in the channel list. A merchant can only use channels enabled for their account; otherwise Gate rejects the request with 403.
  • Amount limit: amount must be greater than 0 and at most 99,999,999.
  • IMID: The merchant account must have an active E-Wallet IMID. If not, Gate rejects the request with 403. Contact Manjo for activation.
  • Idempotency: Callbacks may be re-sent. Handle the same trx_id idempotently.