PASAR API
HTTP Basic auth secret key; dedicated Xendit Malaysia entity. Global, works for MY.
View docs ↗ More Payments APIs# Xendit ~ SEA payment gateway (FPX, e-wallets, VA) needs an API key. # No single public base URL ~ start from the docs: # https://docs.xendit.co/
I'm integrating a Southeast Asian API into my app. API: Xendit ~ SEA payment gateway (FPX, e-wallets, VA) Provider: Xendit Auth: requires an API key (sign up: https://docs.xendit.co/) Pricing: paid Important note: HTTP Basic auth secret key; dedicated Xendit Malaysia entity. Global, works for MY. Source: Xendit (https://docs.xendit.co/) Source type: Provider API or developer docs Endpoint type: Docs-first integration Integration difficulty: Needs API key Last checked: 2026-06-15 Production caveat: Keep credentials server-side and confirm current limits, pricing, and webhook/error behaviour in the provider docs. Help me set up the correct onboarding/authentication path and make the first valid request ~ explain exactly where credentials go and what must happen before production.