Send the invoice.
They pay from it.
Every invoice you send is also a payment page. Your customer opens it, checks the line items, and pays on the spot with a card or Google Pay — no login, no bank details to copy out, no second message from you a week later.
PCI DSS Level 1 · AICPA SOC examined
$18B+ processed · 2.7B transactions · 350,000+ businesses. Processed through PayMongo's licensed Philippine operations since 2019.
Three screens, start to finish
The invoice you write and the page your customer pays on are the same document. Nothing is exported, re-keyed or reconciled by hand.
Write it
Line items, quantities, a discount row and a due date. Add a note if the job needs one — it renders on the invoice your customer reads, not in an email they will lose.
Send it
One link, over whatever channel you already use with this client. Email, chat, a shared thread. There is nothing to install on their side and no account for them to create.
They pay on it
The Pay button opens your checkout inside the same page. The invoice carries its own status until the payment clears, so neither of you has to ask where it stands.
The document
It reads like an invoice, because it is one
Your customer's accounts team will file this. It carries everything they need to do that, and one thing a PDF cannot.
Your brand, not ours
Your name, your mark, your colour on the header and the Pay button. PayMongo appears once, in the footer, as the secured-by line.
Itemised and downloadable
Description, quantity and amount per row, a subtotal, a discount line and a total due. A PDF of the same document is one tap away for whoever files it.
A status the invoice carries itself
Awaiting payment until it clears, and paid after. Your customer sees the same state you do, which is what stops the where-are-we email.
Due dates that read as due dates
The due date is on the document twice — once beside the amount, once in the details — and it changes colour as it approaches.
Before you send one
The questions a serious buyer asks first, answered here so the rest of the page can stay about the product.
Your processor's flow of funds, unchanged. We render the invoice and the checkout page on it; the payment runs on the merchant account you already hold, and the funds reach you the way they reach you today.
No. Invoices sit on the processor you have already been approved for. If you can take a card payment today, you can send an invoice that takes one.
Whatever your processor supports for card-not-present payments — cards, and the network-backed methods your account is enabled for. The invoice shows your customer only the methods that will actually work for them.
It runs through your processor like any other refund on that payment. We do not sit in the middle of it, and there is no separate balance here to reverse it out of.
Yes, subject to what your own processor and merchant account allow. We do not add a market restriction on top of the ones your account already carries.
No, and it says so. The document confirms a payment request from you. An official receipt, where your customer needs one for tax, is yours to issue — that boundary is on the invoice footer so nobody has to guess.
Send your first invoice today
Free to start. No sales call, no integration, no minimum.