PASAR API
Docs are public PDFs (Payment Switch API v2 + Mass Payout API) with HMAC-SHA256 signed requests using merchant credentials; live/test access requires merchant onboarding via sales. PH-first.
View docs ↗ More Payments APIs# Dragonpay ~ OTC and bank payment switch needs an API key. # No single public base URL ~ start from the docs: # https://www.dragonpay.ph/developers
I'm integrating a Philippines API into my app. API: Dragonpay ~ OTC and bank payment switch Provider: Dragonpay Auth: requires an API key (sign up: https://www.dragonpay.ph/developers) Pricing: paid Important note: Docs are public PDFs (Payment Switch API v2 + Mass Payout API) with HMAC-SHA256 signed requests using merchant credentials; live/test access requires merchant onboarding via sales. PH-first. Source: Dragonpay (https://www.dragonpay.ph/developers) Source type: Provider API or developer docs Endpoint type: Docs-first integration Integration difficulty: Needs API key Last checked: 2026-07-03 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.