Platform Overview
Nomad Pay provides merchants with a global cryptocurrency payment service, supporting direct wallet payments, automatic token conversion, and a seamless checkout experience. We offer three primary ways to integrate, from no-code to full developer control:Integration Methods
Method 1: No-Code Payment Link
This is the easiest way to start. You create a product and its settings directly in the Nomad Pay merchant dashboard and generate a shareable URL.- Create Product: Add a product and set its price in your merchant dashboard.
- Generate Link: Generate a payment link for that product.
- Customer Pays: Your customer clicks the link, is taken to a Nomad Pay hosted checkout page, and completes the payment.
- Get Notified: The platform listens for the on-chain transaction and automatically sends a notification to your configured Webhook.
Method 2: Low-Code Widget
This method provides a seamless on-site experience, allowing you to embed our secure checkout component directly into your website.- Embed Script: Add the Nomad Pay JavaScript snippet to your checkout page.
- Configure: Use simple HTML attributes or a JS object to configure the widget (e.g., setting the price, currency).
- Customer Pays: Your customer interacts with the widget on your site to select a token and pay.
- Get Notified: The platform handles the on-chain logic and sends a callback to your Webhook.
Method 3: Pro-Code API
This method provides maximum flexibility and is designed for developers to integrate directly with their backend systems.- Get Keys: Create your API Key Pair (Public Key & Secret Key) in the merchant dashboard.
- Configure Webhook: Configure your Webhook URL in the merchant dashboard to receive notifications.
- Call API: Your server calls the
POST /v1/paymentsendpoint to create a transaction. This request must be signed. - Redirect Customer: You receive a
payment_urlin the response and redirect your customer to this URL. - Get Notified: The platform listens for the on-chain transaction and sends a detailed callback to your Webhook URL. You must verify the signature of this callback.