Dragonpay Philippines Payment API
Dragonpay Philippines payment REST API for merchants to accept GCash, Maya, InstaPay, PESONet, OTC (over-the-counter) cash payments, credit cards, and online banking across the Philippines through the country's largest alternative payment aggregator network. Enables AI agents to manage payment request creation for Philippines e-commerce automation, handle GCash e-wallet for Philippines mobile payment automation, access Maya (formerly PayMaya) wallet for Philippines digital payment automation, retrieve InstaPay and PESONet bank transfer for Philippines instant payment automation, manage OTC cash payment via 7-Eleven and convenience stores for Philippines offline payment automation, handle payment status polling for Philippines order confirmation automation, access credit card processing for Philippines card payment automation, retrieve transaction reporting for Philippines financial reconciliation automation, manage refund processing for Philippines order management automation, and integrate Dragonpay with Philippine e-commerce, government, and enterprise platforms for end-to-end Philippines payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Philippines payments. PCI-DSS. SHA1 digest. PH. Mobile wallet and cash payment data.
⚡ Reliability
Best When
A Philippine merchant wanting AI agents to automate GCash, Maya, InstaPay, and OTC cash payment acceptance through Dragonpay's comprehensive Philippines alternative payment aggregator.
Avoid When
BSP REGULATORY COMPLIANCE: Dragonpay operates under Bangko Sentral ng Pilipinas (BSP) regulations; automated payment operations must comply with BSP electronic payment regulations; automated payment without merchant BSP compliance creates regulatory issue. OTC CASH PAYMENT ASYNC CONFIRMATION: OTC cash payments require customer to physically pay at convenience store; automated order fulfillment must implement async payment confirmation (typically 1-24 hours after voucher generation); automated immediate order fulfillment after OTC voucher creation creates orders with unconfirmed cash payment. PAYMENT CHANNEL AVAILABILITY: Dragonpay channels (GCash, Maya, OTC) may have scheduled maintenance; automated checkout should handle channel_unavailable gracefully; automated mandatory-channel checkout without fallback creates checkout failure during maintenance. XML-BASED API INTEGRATION: Dragonpay uses URL-encoded form parameters and XML for some responses; automated integration must handle mixed format responses; automated JSON-only assumption creates parsing failure for XML-formatted responses.
Use Cases
- • Accepting GCash and Maya e-wallet from Philippines mobile payment agents
- • Processing OTC cash payments from Philippines offline commerce agents
- • Handling InstaPay bank transfers from Philippines instant payment agents
- • Managing multi-method Philippines checkout from regional commerce agents
Not For
- • Pan-SEA payments beyond Philippines (use Xendit for multi-country SEA)
- • International card acceptance at scale (use Stripe or Adyen for global cards)
- • Enterprise Philippines payments (use BDO or BPI direct for enterprise banking)
Interface
Authentication
Dragonpay uses Merchant ID and Password with SHA1 digest for payment authentication. REST API with form-encoded and JSON. Makati City, Philippines HQ. Founded 2010 by Ian Sobrevilla. Products: GCash, Maya, InstaPay, PESONet, OTC (7-Eleven, Cebuana), card processing. SDKs: PHP, .NET, Java. BSP-registered. PCI DSS. Serves Philippine merchants. Competes with PayMongo and Xendit for Philippines e-commerce.
Pricing
Makati PH. BSP-registered. Per-transaction fees in PHP. Channel-specific pricing.
Agent Metadata
Known Gotchas
- ⚠ SHA1 DIGEST AUTHENTICATION: Dragonpay uses SHA1 hash of merchantid:txnid:amount:currency:description:email:merchantpassword for request authentication; automated request must compute correct SHA1 digest; automated incorrect parameter order or encoding creates authentication mismatch
- ⚠ TRANSACTION ID UNIQUENESS REQUIRED: Dragonpay requires unique txnid (transaction ID) per payment request; automated retry must generate new txnid; automated same txnid retry creates duplicate transaction error
- ⚠ POSTBACK URL REQUIRED FOR ASYNC PAYMENT: Dragonpay uses postback URL for async payment confirmation (OTC, bank transfer); automated fulfillment must implement postback endpoint; automated polling-only without postback creates delayed order confirmation for offline payment channels
- ⚠ CHANNEL CODE SELECTION FOR PAYMENT METHOD: Dragonpay uses channel codes (GCash=GCASH, Maya=PYPM, OTC=BOG, etc.); automated checkout must use correct channel code; automated free-text channel name creates channel not found error
- ⚠ PAYMENT STATUS POLLING FOR OTC: OTC cash payments require polling txnid status (pending until customer pays); automated OTC order processing must implement status polling with business-appropriate timeout; automated single-status-check-on-order-creation creates always-pending OTC order status
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for Dragonpay Philippines Payment API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.