Skip to main content

Midtrans payment gateway action — auth status check-in

Context​

Dimas Fauzi Hidayat asked Eko Aprianto for a status check on payment-gateway action work, specifically whether Midtrans auth is the only one ready so far.

Notes​

  • Midtrans auth is not ready yet (Eko: "Blm ada mas").
  • What was done previously on Midtrans: backend side only. Not yet done on FE, and not yet tested.
  • Midtrans auth cannot reuse the existing auth mechanism as-is. It differs from what's currently supported:
    • token lifetime is 15 minutes;
    • token request requires a signature and client-key.
  • Eko's assessment: a dedicated Midtrans auth type is needed, similar in shape to how Google OAuth or HMAC-style auth is handled.

Decisions / changes​

None — this is a status check-in, no decision recorded yet.

Follow-ups​

  • TBD (owner) — decide whether to build a dedicated Midtrans auth type (signature + client-key, 15-min token lifetime) and reflect that in the RFC's auth design if it isn't already covered.
  • TBD (owner) — complete Midtrans BE auth, build FE, and test, before relying on it in the native-integration flow.