Most invoicing tools decide for you which payment methods exist. If your client pays by M-Pesa, or by a deposit at a branch, or by handing cash to an agent, those tools have no answer and you end up taking the payment outside the invoice. PaidSeal works the other way round. You switch on the methods your clients already use, and when the method they use is not on the list, you describe it and it gets built.
Open Payment Methods and enable the ones you want to appear. Cards, bank transfer (pay-by-bank or ACH), Apple Pay, Google Pay and PayPal are available from the start. So are the account-to-account methods people actually ask about: Venmo, Cash App and Zelle. Local mobile money sits in the same list, including M-Pesa, MTN MoMo and Orange Money.
Enabling a method does not commit you to it everywhere. The methods you switch on become the menu on your pay page, and you decide which ones belong on a given invoice. A retainer client who always pays by bank transfer does not need six buttons.
This is the part no card-only tool can do. Type one sentence describing how you get paid, and PaidSeal works out the three things a payment method needs: what your client sees, where the money goes, and how the payment gets confirmed.
Sentences that work:
You get a draft, not a live method. Check the number, fix the wording your client will read, then save it. From that point it appears on your invoices like any other option.
Two different things happen depending on the method, and the difference matters for your records.
| Method | How the invoice clears |
|---|---|
| Card, Apple Pay, Google Pay, PayPal through your connected account | The processor reports the payment and the invoice marks itself paid |
| A method PaidSeal can read through an API | Same: it reconciles on its own |
| A transfer straight into your account, cash, a branch deposit | Your client says they have sent it, the invoice waits, and it only turns paid when you confirm the money arrived |
Nothing is ever marked paid on a client's word alone. For manual methods the invoice sits in a reported state, which is visible to you and to the client, until you confirm. That is the whole point of the design: you keep a record that reflects money you actually have.
One hosted pay page, showing the invoice and the methods you enabled. No account, no password, no app to install. For a card they pay on the processor's secure page, so card numbers never touch your device or your site. For a manual method they get your instructions plus a button to tell you it is sent. Both of you get a receipt either way.
The plan limit counts custom methods, the ones you describe yourself.
| Plan | Custom payment methods |
|---|---|
| Free | 1 |
| Pro | 5 |
| Business | Unlimited |
One is enough to test the thing properly. Set up the local rail your clients actually use, send a real invoice, and watch it come back confirmed before you pay for anything.
Can I put Zelle on an invoice? Yes. Zelle moves money bank to bank and has no invoicing API, so the invoice carries your Zelle details and the payment clears when you confirm it landed.
Can I invoice through Venmo or Cash App? You can offer them as methods on the pay page. Whether a given payment reports back on its own depends on how that method is connected, which the Payment Methods screen tells you when you enable it.
My client wants to pay cash. Describe it as a method once, with where and who, and cash stops being the thing that lives outside your books.
Do they need a PaidSeal account? No. The pay page is a link.
Related: Connect Stripe or PayPal · Match payments to invoices · Mobile money on invoices · Getting paid without Stripe