Getting Started
Overview
How the embedded checkout fits together.
Documentation categories
Use the top navigation to choose the implementation layer that matches the merchant or developer workflow.
- Guides covers hosted checkout, embeds, redirects, branding, and operational troubleshooting.
- E-commerce plugins covers WordPress, Shopify, PrestaShop, OpenCart, Magento, and Wix integrations.
- SDK Libraries covers official PHP and JavaScript SDKs for backend payment-link creation and webhook verification.
- Developer Apps covers OAuth applications, delegated company access, scopes, and app webhooks.
- API Reference covers authentication, payment-link routes, customer portal URLs, webhooks, and object models.
- API Testing opens the live request console for signed-in teams.
Public endpoints
Use the hosted checkout as the canonical fallback, the embedded checkout for iframe modal flows, and the modal script for host-page integration.
Hosted checkout
Full-page payment link route.
https://makepay.io/payment/YOUR_PAYMENT_UIDEmbedded checkout
Iframe-ready payment flow.
https://makepay.io/embed/payment/YOUR_PAYMENT_UIDModal script
Browser script for host pages.
https://makepay.io/modal/makepay.jsIntegration model
MakePay keeps payment-link configuration in MakeCrypto and lets the merchant site decide how checkout is launched. The same payment UID works in hosted and embedded modes, and the partner API can create and manage those UIDs from your backend.
- Use the hosted route when you want a direct payment page.
- Use the embedded route when the checkout is displayed in a modal iframe.
- Use the modal script when the merchant page owns the button, callbacks, and redirect behavior.
- Use the MakePay payment-link API when orders or invoices should create payment links automatically.
Next step
Start with the quick-start guide for the modal embed path, or open the API quick start when your backend needs to create payment links directly.