Start a MakePay crypto payment from a plain HTML form
Form-submit payments are the simplest MakePay integration path for pages that can post predefined fields and redirect customers to hosted crypto checkout.
Form payments · 6 min read · Updated 2026-04-27
Not every payment flow needs an SDK on day one. A marketing page, donation form, event deposit page, or internal order form might only need to collect a few fields and start hosted checkout.
MakePay form-submit payments support that simple path. A form posts amount, currency, customer context, and redirect fields to MakePay, then the customer lands on hosted checkout.
When form payments are enough
A form-submit flow is good for simple fixed-price or customer-entered payment requests where you do not need a full backend integration immediately.
It is also useful as a fallback path for static sites, landing pages, and campaigns that want to validate payment demand before investing in a deeper API build.
When to move to API or SDKs
Move to the API, PHP SDK, or NPM SDK when your system needs strict server-side amount control, inventory reservation, account entitlements, webhook automation, or custom reconciliation.
The form flow can start payments, but your operations still need a reliable way to decide when an order is paid.
Security boundaries
Do not trust customer-editable form fields for high-value orders without server-side validation. For sensitive amounts, generate the payment request on your backend and redirect to a hosted payment link.
Use success and failure URLs for customer navigation, but use signed webhooks or dashboard status for business decisions.
Questions before you start.
Can a static site use MakePay form payments?
Yes, for simple flows. Sensitive pricing and fulfillment decisions should still be verified through a trusted backend or dashboard process.
Are redirects enough to mark an order paid?
No. Redirects are for customer navigation. Use signed webhooks or verified payment status for order fulfillment.