ForjioHuudisIdentityPlugipayPaymentsStorlaunchE-commerceFulkrumaFulfilmentRiplloMarketingLinkSnapShort URLsPawpadoGPU streaming
Plugipay Docs
⌘K

Midtrans (BYO)

Midtrans (GoTo Financial) is Indonesia's largest payment gateway. Connect your existing Midtrans account to Plugipay and we orchestrate payments through it.

Why use Midtrans BYO

  • You already have Midtrans. Most Indonesian merchants do.
  • Direct relationship. Settlement to your Midtrans balance and bank.
  • Direct Midtrans support for provider-specific issues.
  • Lower Plugipay fees vs. managed mode (you're providing the provider).

What you need

  1. A Midtrans account (Snap or Core API, either works for our integration).
  2. Server Key (Midtrans dashboard → Settings → Access Keys).
  3. Client Key (same screen).
  4. Optional: Merchant ID for cross-validation.

Connecting

  1. Plugipay: Settings → Payment methods → Add provider → Midtrans.
  2. Choose sandbox or production.
  3. Paste server key and client key.
  4. Click Connect. We verify with a test API call.

After connecting, configure Midtrans webhooks:

  • Midtrans dashboard → Settings → Configuration → Payment Notification URL
  • Set to: https://api.plugipay.com/v1/inbound-webhooks/midtrans/<your-workspace-id>
  • Save

Payment methods

Method Status
Cards (Visa, MC, JCB, AmEx) ✅
Bank transfer (VA: BCA, Mandiri, BNI, BRI, Permata, CIMB) ✅
E-wallets (GoPay, ShopeePay, OVO via Snap) ✅
QRIS ✅
Retail outlets (Alfamart, Indomaret) ✅
BCA KlikPay / Mandiri ClickPay / CIMB Clicks ✅ if enabled on your Midtrans
Akulaku PayLater ✅ if enabled

We mirror your Midtrans configuration — methods you enable there appear in Plugipay.

What Plugipay adds

Same as the Xendit BYO section: unified API, hosted checkout pages, webhook normalization, templates, idempotency, cross-provider portability.

What Midtrans handles

  • Money movement and settlement to your bank account
  • Underlying PCI compliance
  • Card disputes (visible in Midtrans dashboard)
  • Customer-facing receipts (Midtrans sends one in addition to ours; you can disable Midtrans's via their settings if redundant)

Refunds

Refund requests forward to Midtrans's refund API. Timing:

  • Cards: 14 business days (Midtrans's standard)
  • Bank transfer / e-wallet: 1-3 business days
  • QRIS: near-instant

The refund object's status reflects Midtrans's state.

Snap vs Core API

Midtrans has two integration patterns: Snap (hosted page) and Core API (you build the UI). Plugipay supports both:

  • If you've integrated Snap previously, our hosted checkout works on top — Midtrans never sees Snap-specific events because we redirect users to Plugipay's checkout instead.
  • If you've integrated Core API previously, Plugipay's API gives you a higher-level interface. You don't need to construct Midtrans payloads directly.

In both cases, the keys are the same and the connection works identically.

Fees

Midtrans's fee schedule applies; Plugipay charges a separate BYO platform fee on top. Both show on each payment as fees.provider and fees.platform.

Notes

  • Sandbox keys won't process production payments, regardless of API calls. Always verify the environment before going live.
  • Midtrans takes longer for card refunds than other providers (up to 14 business days vs Xendit's 5-10). If fast refunds are critical, Xendit may be a better fit.
  • 3D Secure is supported and required for many Indonesian-issued cards.

Next

Plugipay — Payments that don't tax your success