A checkout that offers what your buyers actually use
GCash, Maya, Visa and Mastercard, online bank transfer through Dragonpay, over-the-counter payment, instalments where your provider supports them, and cash on delivery. Methods are ordered by what your customers pick most, and the whole flow is built for a phone on mobile data, because that is where the majority of Philippine checkouts happen.
Gateway setup done properly, once
We help you prepare what PayMongo, Dragonpay, Xendit or your bank asks for, then configure the keys your provider issues to you, test in sandbox against real scenarios and switch to live. Your credentials stay yours — we work in your accounts, never around them, and hand over documentation for every setting we touch.
Recurring billing, deposits and instalments
Subscriptions charged automatically, reservation fees followed by a balance, tuition or rent billed monthly with reminders before the due date. Failed recurring charges retry on a schedule and notify the customer, so a card that expired does not quietly become a lapsed account nobody noticed for two months.
Cash on delivery and offline payments, tracked the same way
COD orders carry the amount the rider must collect, and remittance from J&T, Lalamove or your own drivers is recorded against those orders. Bank deposits and in-branch payments are logged with reference numbers. Every payment route ends in the same ledger, which is the only way the totals ever agree.
Refunds, partial payments and failed transactions
Refund in full or in part from the admin panel with the reason recorded and the customer notified. Partial payments leave a visible balance rather than an order that looks paid. Failed and abandoned transactions are kept with their error, so you can see whether you are losing checkouts to a specific method or bank.
Reconciliation and settlement reporting
Transactions matched against orders, gateway fees separated out, and settlements compared to what actually landed in the bank. Unmatched payments sit in an exceptions list until someone resolves them instead of disappearing. This is the module that earns the build back — most disputes are matching problems, not payment problems.
Security handled where it belongs
Card data is captured by the gateway on their PCI-DSS certified infrastructure and never touches your server, so you hold tokens rather than card numbers. 3D Secure is enforced where the provider requires it, webhooks are signature-verified so payment confirmations cannot be faked, and every status change is logged with a user and a timestamp.