Overview

Use a prebuilt checkout page to start accepting online payments.

Embedded form (iFrame)
Paywint-hosted page (redirect)
Inline Checkout SDK

Embed the Paywint checkout inside your website using an iFrame.
This option keeps customers inside your UI while Paywint handles all sensitive data and compliance.

Create a payment link

Your backend calls Create Payment Link with the amount and payer information.

Receive the checkout URL

Paywint returns a payment_link URL representing the checkout session.

Embed the checkout

You load the payment_link inside an <iframe> on your website.

Customer completes the payment

The customer reviews and completes the payment inside the embedded checkout.

Receive lifecycle webhooks

Paywint sends webhook notifications to your server as the payment progresses
(session opened, status updates, and final result).
For full event details, see the Webhooks documentation.

Redirect the customer

After the checkout finishes, Paywint redirects the customer to the Redirect URL
that you configure in your merchant dashboard.
The redirect includes the final payment status, and your application should handle
the next steps based on that status.

Redirect customers to Paywint-hosted checkout page.This option gives you the fastest setup with no front-end integration work. Customers leave your site, complete the payment on Paywint’s secure checkout page, and are redirected back to you once the payment finishes.

Create a payment link

Your backend calls Create Payment Link with the relevant payment details.

Receive the checkout URL

Paywint returns a payment_link URL that represents the hosted checkout page.

Redirect the customer

Your front-end navigates the customer to the payment_link
(typically by opening it in a new window or redirecting the browser).

Customer completes the payment

The customer completes the entire checkout process on Paywint’s hosted page.
All sensitive data entry and validation is handled by Paywint.

Receive lifecycle webhooks

As the payment moves through different states, Paywint sends corresponding webhook notifications to your server.
Refer to the Webhooks documentation for all available event types.

Customer is returned to your application

After the checkout completes, Paywint redirects the customer to the Redirect URL
configured in your merchant dashboard.
The redirect includes the final payment status, and your application should display
a confirmation, error message, or next step based on that status.

Build a fully custom checkout experience using Paywint-managed UI components. Your backend issues a short-lived checkout token, the frontend SDK handles OTP verification, card validation, and payment — all within your own UI.

Issue a checkout token (your backend)

Your backend calls the appropriate token endpoint, passing the payer identity, payment amount, currency, and scope.Paywint returns a short-lived checkout_token (valid for 30 minutes).

Generate Checkout Token Here

Initialize the SDK (frontend)

Pass the checkout_token to the Paywint Inline Checkout SDK along with the payment amount and currency.

const pwCheckoutConfig = {
  token: "CHECKOUT_TOKEN_FROM_YOUR_BACKEND",
  payOptions: ["card", "wallet"],
  amount: 120,
  currency: "USD",
  invoice_number: "INV-1001",
  description: "Order #1001"
}
pwCheckout.init("#checkout-root", pwCheckoutConfig, (event) => {
  console.log(event.event, event.message, event.data);
});

View Complete Implementation Here

Receive lifecycle webhooks (your backend)

As the payment moves through states, Paywint sends webhook notifications to your server. See the Webhooks documentation for all available event types and payload shapes.

Users

KYC & KYB

Wallet

Payments

Accept Payments

Bank Accounts

Paywint Bank Accounts

Cards

Check

Payee Management

Payee Bank Accounts

Payee Cards

Payee Addresses