Getting Started

Overview

Choose the MakePay documentation path for your workflow.

Documentation sections

Start with the workflow you are building, then move into the exact API, embed, plugin, or operational guide you need.

Get Started

Set up the first checkout flow, then choose the API surface that matches your stack.

Quick startCreate a payment UID and render the first MakePay button.API quick startCreate a MakePay API key and send your first server request.AuthenticationUse key headers, scoped permissions, and rotation safely.

Receive Payments

Launch hosted checkout, embedded modal flows, and payment-link automation.

Payment links APICreate, list, inspect, pause, archive, and email checkout links.Anonymous payment APICreate no-account one-time checkout links with explicit settlement and optional webhooks.Form submit paymentStart hosted checkout from plain HTML without an API client.WebhooksVerify signed payment, subscription, and delivery events.

Convert & Manage

Control customer access, checkout presentation, settlement fields, and live operations.

Customer portal APIGenerate signed URLs for customer-managed billing sessions.BrandingApply merchant colors and checkout theme behavior.API testingRun live requests with the selected team and MakePay key.

Integrations

Embed MakePay in your product, install commerce plugins, or connect partner apps.

Embed modeUse declarative buttons or the browser API for embedded checkout.SDK librariesUse official PHP, Go, Python, JavaScript, Rust, Java, and Swift SDKs.E-commerce pluginsInstall ready-made integrations for popular commerce platforms.Developer appsCreate OAuth apps for delegated company access and webhooks.

What you can build

MakeCrypto documentation is organized around real MakePay implementation paths, from hosted payment links to partner applications and migration work.

Hosted checkoutRedirect buyers to a MakePay payment page with a stable fallback URL.Embedded checkoutOpen the same payment UID inside an iframe modal owned by the merchant site.Server-created linksCreate payment links from orders, invoices, bookings, donations, and custom backends.Anonymous API paymentsGenerate hosted payment requests without an account or API key by sending a public one-time payload.Platform pluginsConnect stores and communities with OAuth, hosted checkout, and signed callbacks.Partner applicationsRequest delegated access and call MakeCrypto APIs with scoped OAuth tokens.Provider migrationsUse agent-ready guides to move from existing crypto payment providers to MakePay.

Why MakeCrypto

Use one payment-link model across checkout surfaces, APIs, plugins, SDKs, and webhooks so merchant teams can start simple and keep the same integration as their workflow grows.

One payment UIDThe hosted page, embedded checkout, and modal script all resolve from the same payment identifier.API-first operationsPayment links, customer portal URLs, webhooks, settings, and destination assets share one authenticated API model.Commerce-ready pathsStart with no-code plugins, plain HTML forms, SDKs, or partner OAuth depending on the integration owner.Recovery guidesUse troubleshooting, redirect handling, and migration checklists when a checkout flow needs operational clarity.

Public endpoints

Use the hosted checkout as the canonical fallback, the embedded checkout for iframe modal flows, the modal script for host-page integration, and the anonymous payment API when a one-time request should work without an account or API key.

Hosted checkout

Full-page payment link route.

https://www.makepay.io/payment/YOUR_PAYMENT_UID

Embedded checkout

Iframe-ready payment flow.

https://www.makepay.io/embed/payment/YOUR_PAYMENT_UID

Modal script

Browser script for host pages.

https://www.makepay.io/modal/makepay.min.js

Integration 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.
Use the anonymous payment API when a one-off payment request carries its own settlement route, branding snapshot, and optional webhook.

Next step

Start with the quick-start guide for the modal embed path, open the API quick start when your backend needs authenticated merchant links, or jump straight to anonymous payment links for no-account one-time payments.