Stablecoin Checkout - Blockradar

In a nutshell
Blockradar Checkout lets you accept stablecoin payments via shareable links—no customer accounts or complex integrations required. Create a link, share it, and receive payments directly to your wallet.

Prerequisites

Before creating payment links, ensure you have:

API Key

Get your API key from the Blockradar Dashboard. Navigate to Developers to generate one.

Master Wallet Created

Create a master wallet in the dashboard (see Create a Master Wallet). Payment links are tied to a wallet.

Checkout Plan Active

Ensure the Checkout feature is enabled on your account. Contact [email protected] if you need to activate it.

Webhook Configured (Optional)

Set up webhooks to receive real-time payment notifications. See Webhooks for setup details.

Introduction

Payment links are shareable URLs that allow anyone to send stablecoin payments to your wallet. They’re perfect for:

E-commerce: Send to customers for product purchases
Invoicing: Include in invoices for services rendered
Donations: Share on social media or websites
Marketplace payments: Facilitate peer-to-peer transactions
Subscription billing: Recurring payment collection

How Payment Links Work

Creation

Create a payment link with specific parameters like amount, name, description, and payment limits.

Sharing

Share the generated URL with your customers through email, messaging, or embed it on your website.

Payment

Customers click the link, enter their payment details, and complete the transaction.

Confirmation

You receive webhook notifications and can track payment status in real-time.

Payment Link Features

Customizable Parameters: Set amount, description, payment limits, and metadata
Shareable URLs: Generate unique payment links for each transaction
Customer Pre-filling: Pre-populate customer details via URL query parameters
Real-time Tracking: Monitor payment status and receive webhook notifications
Multi-network Support: Accept payments across different blockchain networks
Auto-sweep Integration: Funds automatically consolidated to master wallet

Multi-Asset Support

USDT, USDC, DAI, BUSD across multiple blockchains
Ethereum, BSC, Polygon, Base, Arbitrum, Optimism, Tron, Solana, Celo
Automatic conversion and routing for optimal user experience

Flexible Configuration

Fixed amounts for specific products/services
Variable amounts for donations or custom payments
Payment limits to ensure timely payments
Custom metadata for tracking and analytics
Webhook notifications for real-time updates

Security & Compliance

AML screening on all incoming payments
Address validation and verification
Fraud detection and prevention
Regulatory compliance across jurisdictions

Payment Flow

1. Payment Link Creation

When you create a payment link, Blockradar returns a unique payment URL:

{
  "id": "pl_123456789",
  "name": "Product Purchase",
  "url": "https://pay.blockradar.co/payment-link-10012",
  "amount": "100.00",
  "currency": "USD",
  "active": true
}

2. Customer Pre-filling with Query Parameters

You can enhance the payment URL with query parameters to automatically pre-fill customer details on the payment page:

https://pay.blockradar.co/payment-link-10012?name=Customer&[email protected]&reference=ORDER123&amount=99.99&redirectUrl=https://yoursite.com/payment-success

Supported Optional Query Parameters:

name - Customer’s name (appears on payment page)
email - Customer’s email address
reference - Custom reference that will be included in transaction responses
amount - Amount shown to the customer on the payment page. It is display-only: Blockradar does not store it or check the payment against it (see When the Amount Received Differs)
redirectUrl - URL to redirect to after payment completion

3. Post-Payment Redirect

When a redirectUrl is provided, customers will be automatically redirected to your specified URL after payment processing is complete. The redirect URL will include the following query parameters: Redirect Query Parameters:

status - Payment status (success, failed, pending)
tx_reference - Transaction reference ID
reference - Your custom reference (if provided)
slug - Payment link identifier

Example Redirect URL:

https://yoursite.com/payment-success?status=success&tx_reference=tx_abc123&reference=ORDER123&slug=payment-link-10012

The redirect only occurs after payment processing is complete. If no redirectUrl is provided, customers will see the default payment completion page.

4. Amount Configuration

Payment links support two amount modes: Fixed Amount (Pre-set)

When you specify an amount during creation, customers cannot modify the payment amount
Ideal for specific products or services with set pricing
Example: Product purchase for exactly $99.99

Variable Amount (Customer Input)

When no amount is specified, customers can enter their own payment amount
Perfect for donations, tips, or flexible pricing scenarios
Customers see an amount input field on the payment page

Only the link’s own amount sets the amount Blockradar expects. The amount query parameter changes what the payment page shows, not what Blockradar checks.

5. Payment Processing

Customers visit the payment link, review pre-filled details, and complete the transaction using their preferred stablecoin.

6. Transaction Response

The reference parameter from the URL will be included in the transaction response and webhook payloads, allowing you to link payments back to your internal systems.

When the Amount Received Differs

Customers send stablecoins from their own wallet or exchange, so the amount that arrives can differ from the amount on the payment page. They may type a different number, or an exchange may deduct its withdrawal fee from the amount sent. How Blockradar records the payment depends on whether the link has a fixed amount.

Link	Customer sends	Status	Webhook
Fixed amount (`100.00`)	`100.00` or more	`SUCCESS`	`deposit.success`
Fixed amount (`100.00`)	Less than `100.00`	`INCOMPLETE`	`deposit.incomplete`
No amount	Any amount	`SUCCESS`	`deposit.success`

In every payload, amountPaid is what the customer has actually sent. On a fixed-amount link, amount is the link’s amount converted to the token paid and rounded down to that token’s decimals, so an overpayment of 100.50 arrives with amount: "100" and amountPaid: "100.5". On a no-amount link, amount and amountPaid are both what was received.

Credit customers from amountPaid, never from the amount you asked for. On a no-amount link, a customer who was asked for 100.00 and sends 95.00 still produces a deposit.success webhook, with amountPaid: "95". Crediting the requested amount over-credits every underpayment.

Underpaid Fixed-Amount Links

A payment below the link’s amount is marked INCOMPLETE and sends a deposit.incomplete webhook. Any shortfall counts, even a fraction of a cent. The payload has the same fields as deposit.success, with the total received so far in amountPaid and two extra keys in metadata:

remainingAmount: how much is still due
partialPayments: one entry per on-chain payment received, with its hash, amount and senderAddress

{
  "event": "deposit.incomplete",
  "data": {
    "id": "0d7a0b98-943c-48d0-8baa-216c29956050",
    "status": "INCOMPLETE",
    "amount": "100",
    "amountPaid": "95",
    "metadata": {
      "partialPayments": [
        {
          "senderAddress": "0x451dEFC27B45808078e875556AF06bCFdC697BA4",
          "recipientAddress": "0x9D8dF15628B737CAf63a92Abd8E8bb304210eA94",
          "amount": "95",
          "type": "DEPOSIT",
          "hash": "0x9f01af8f517afb3fd3ee17f36dabee03a4d6514885473115815de86c28ea7dfb",
          "blockNumber": 34771099,
          "logIndex": 0,
          "createdAt": "2025-08-27T21:52:19.839Z"
        }
      ],
      "remainingAmount": "5"
    }
  }
}

The example shows only the fields specific to this event. metadata also keeps any metadata you set on the payment link. If the customer sends the rest to the same payment address while it is still active, Blockradar adds it to amountPaid. A payment that still leaves the total short sends another deposit.incomplete. The payment that reaches the link’s amount makes the transaction SUCCESS and sends deposit.success with the cumulative amountPaid. Every event carries the same transaction id. Don’t wait for a deposit.incomplete before every deposit.success. If the final payment arrives while an earlier deposit.incomplete is still being retried, that delivery is dropped and only deposit.success is sent.

Credit by transaction id, not per event. Keep a running total of what you have credited for each id. On each deposit.incomplete or deposit.success, credit amountPaid minus that total, and ignore the event if the result is zero or less. This handles partial payments, retried deliveries and events that arrive out of order. If you only credit completed payments, act on deposit.success and use deposit.incomplete to tell the customer how much is still due.

To review underpaid payments, list a link’s transactions with status=INCOMPLETE (see Fetching Payment Link Transactions) and compare amount with amountPaid.

Charging a Different Amount per Customer

If the amount varies per order, create a payment link without an amount and pass each order’s amount and reference in the URL:

https://pay.blockradar.co/payment-link-10012?amount=99.99&reference=ORDER123

The customer sees 99.99 on the payment page. Whatever they send, the payment completes and you receive deposit.success with that reference. Compare amountPaid with the order total on your side, and decide there how to handle a shortfall or an excess.

Try It Out

Experience Blockradar payment links firsthand with our live demo: 🔗 Demo Payment Link: https://pay.blockradar.co/demo This demo showcases:

Payment Flow: Complete customer experience from link to completion
UI/UX: Modern, intuitive payment interface
Stablecoin Options: Multiple payment methods and networks
Real-time Updates: Live transaction status and confirmations

The demo payment link is for testing purposes only. No real transactions will be processed.

Creating Payment Links

Basic Payment Link

Create a simple payment link for a fixed amount:

{
  "name": "Product Purchase",
  "description": "Payment for Laptop Pro 2024",
  "amount": "100.00",
  "redirectUrl": "https://store.example.com/thank-you",
  "successMessage": "Thank you for your purchase!",
  "metadata": "{\"product_id\": \"prod_123\", \"order_id\": \"ord_456\"}"
}

Variable Amount Payment Link

Allow customers to choose their payment amount:

{
  "name": "Donation Campaign",
  "description": "Support our disaster relief efforts",
  "redirectUrl": "https://charity.example.com/thank-you",
  "successMessage": "Thank you for your generous donation!",
  "metadata": "{\"campaign\": \"disaster_relief_2024\"}"
}

Payment Link with File Upload

Include a file (e.g., invoice, product image) with your payment link using form-data: Form Data Fields:

name: Service Invoice
description: Web development services - January 2024
amount: 1500.00
redirectUrl: https://company.example.com/payment-success
successMessage: Payment received! We’ll start working on your project.
metadata: invoice_id: INV-2024-001, service: web_development
file: [cover.png] (file upload)

When including file uploads, use form-data instead of JSON. The file will be stored and accessible via the payment link.

Payment Link Parameters

Required Parameters

Parameter	Type	Description
`name`	string (max: 250)	The name of the payment link

Optional Parameters

Parameter	Type	Description
`description`	string (max: 250)	A description of the payment link
`slug`	string (max: 250)	A unique identifier (URL-friendly). Must match regex: `^[a-zA-Z0-9-]+$`
`amount`	string	The amount for the payment link. Must be a valid string number > 0
`redirectUrl`	string (URL)	The URL to redirect the user after payment. Must include http:// or https://
`successMessage`	string (max: 500)	Message shown when the payment succeeds
`inactiveMessage`	string (max: 500)	Message shown when the payment link is inactive
`metadata`	object (JSON string)	Custom metadata as key-value pairs (string or number). Must be sent as a JSON string in form-data
`paymentLimit`	number (min: 1)	Maximum number of payments allowed for this link
`file`	file	An optional file upload (e.g., image or document) attached to the payment link

Payment Flow

Customer Experience

Click Payment Link
- Customer receives and clicks the payment link
- Link opens to a secure payment page
Select Payment Method
- Choose from available stablecoins
- Select preferred blockchain network
- Enter payment amount (if variable)
Complete Payment
- Customer confirms transaction details
- Payment is processed on the blockchain
- Real-time confirmation and status updates
Success Confirmation
- Payment confirmation page
- Optional redirect to your website
- Receipt and transaction details

Merchant Experience

Real-time Notifications
- Webhook events for payment status
- Email notifications (if configured)
- Dashboard updates
Payment Tracking
- Transaction history and status
- Payment analytics and reporting
- Integration with your systems

Address Lifecycle

Payment addresses generated for checkout links have a limited lifecycle:

After successful payment: The address is immediately deactivated and cannot receive additional payments
After 24 hours of inactivity: If no payment is made to an address within 24 hours, it is automatically deactivated

Each new payment session generates a fresh address. This ensures security and prevents address reuse.

Webhook Events

Payment links trigger the following webhook events when payments are received:

Event	Description
`deposit.success`	Payment was received via the payment link
`deposit.incomplete`	An underpayment was received on a fixed-amount link. See Underpaid Fixed-Amount Links
`deposit.failed`	Payment attempt failed

Webhook Payload Example

{
  "event": "deposit.success",
  "data": {
    "id": "0d7a0b98-943c-48d0-8baa-216c29956050",
    "reference": "bjXPk7d00",
    "senderAddress": "0x451dEFC27B45808078e875556AF06bCFdC697BA4",
    "recipientAddress": "0x9D8dF15628B737CAf63a92Abd8E8bb304210eA94",
    "tokenAddress": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "1",
    "amountPaid": "1",
    "amountUSD": "1",
    "rateUSD": "1",
    "fee": null,
    "feeHash": null,
    "currency": "USD",
    "toCurrency": null,
    "blockNumber": 34771099,
    "blockHash": "0xa9dc060dbe649676a15ae1faee725851fe1ecf2401b200e60fff33fc0ff41e84",
    "hash": "0x9f01af8f517afb3fd3ee17f36dabee03a4d6514885473115815de86c28ea7dfb",
    "confirmations": 6,
    "confirmed": true,
    "gasPrice": "7026436",
    "gasUsed": "62159",
    "gasFee": "0.000000436756235324",
    "status": "SUCCESS",
    "type": "DEPOSIT",
    "note": null,
    "amlScreening": {
      "provider": "ofac, fbi, tether, circle",
      "status": "success",
      "message": "Address is not sanctioned"
    },
    "assetSwept": true,
    "assetSweptAt": "2025-08-27T21:53:22.300Z",
    "assetSweptGasFee": "0.000000489848406004",
    "assetSweptHash": "0xe85efcf15ff8eaa2429aea32515347d65ff8098f22dac567611c258441bde809",
    "assetSweptSenderAddress": "0x9D8dF15628B737CAf63a92Abd8E8bb304210eA94",
    "assetSweptRecipientAddress": "0xb55c054D8eE75224E1033e6eC775B4F62D942b43",
    "assetSweptAmount": "1",
    "reason": "Funds swept successfully",
    "network": "mainnet",
    "chainId": 8453,
    "metadata": {},
    "toAmount": null,
    "signedTransaction": null,
    "rate": null,
    "createdAt": "2025-08-27T21:52:19.839Z",
    "updatedAt": "2025-08-27T21:53:22.303Z",
    "asset": {
      "id": "3a18a31a-86ad-44a0-9b9c-cdb69d535c64",
      "name": "USD Coin",
      "symbol": "USDC",
      "decimals": 6,
      "address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
      "standard": null,
      "currency": "USD",
      "isActive": true,
      "logoUrl": "https://res.cloudinary.com/blockradar/image/upload/v1716800083/crypto-assets/usd-coin-usdc-logo_fs9mhv.png",
      "network": "mainnet",
      "isNative": false,
      "createdAt": "2024-06-08T12:59:11.303Z",
      "updatedAt": "2025-06-03T11:34:36.288Z"
    },
    "address": {
      "id": "824d8ff9-1ee4-43d1-bec0-c77f25699cd6",
      "address": "0x9D8dF15628B737CAf63a92Abd8E8bb304210eA94",
      "name": null,
      "isActive": true,
      "type": "INTERNAL",
      "derivationPath": "m/44'/60'/0'/0/503",
      "metadata": null,
      "configurations": {
        "aml": {
          "status": "success",
          "message": "Address is not sanctioned",
          "provider": "ofac, fbi, tether, circle"
        }
      },
      "network": "mainnet",
      "createdAt": "2025-08-27T21:52:19.839Z",
      "updatedAt": "2025-08-27T21:52:19.839Z"
    },
    "blockchain": {
      "id": "28a730d3-211b-40f7-bb8f-dd589dcc738e",
      "name": "base",
      "symbol": "eth",
      "slug": "base",
      "derivationPath": "m/44'/60'/0'/0",
      "isEvmCompatible": true,
      "isL2": true,
      "logoUrl": "https://res.cloudinary.com/blockradar/image/upload/v1716800080/crypto-assets/Base_Network_Logo_vqyh7r.png",
      "isActive": true,
      "tokenStandard": null,
      "createdAt": "2024-06-07T11:09:56.586Z",
      "updatedAt": "2025-11-26T15:26:21.825Z"
    },
    "wallet": {
      "id": "6b741fbc-8a9c-48a1-92b0-ae7b52de8b9e",
      "name": "Base Mainnet Wallet",
      "description": "This is base mainnet wallet",
      "address": "0xb55c054D8eE75224E1033e6eC775B4F62D942b43",
      "derivationPath": "m/44'/60'/0'/0/0",
      "isActive": true,
      "status": "ACTIVE",
      "network": "mainnet",
      "configurations": {
        "withdrawal": {
          "gasless": {
            "isActive": true
          }
        },
        "autoSweeping": {
          "isActive": true
        }
      },
      "createdAt": "2024-06-15T02:53:23.409Z",
      "updatedAt": "2025-08-18T23:26:13.469Z",
      "business": {
        "id": "a109729b-3b97-4fb3-a90a-769a0cbf6a25",
        "name": "Blockradar",
        "sector": "infrastructure",
        "userId": "831b739e-ed85-499a-b273-8a1a5b41b7a0",
        "status": "ACTIVE",
        "pipedriveOrganizationId": "308",
        "createdAt": "2023-04-28T17:40:18.541Z",
        "updatedAt": "2025-06-19T23:51:01.019Z"
      }
    },
    "beneficiary": null,
    "paymentLink": {
      "id": "dd8eb830-0971-4f61-97bc-b1ad352e1c48",
      "name": "Blockradar Checkout Demo",
      "description": "Blockradar payment links simplify stablecoin transactions into a clean, intuitive experience. This demo shows how users can pay securely using stablecoins with just a few clicks, fast, transparent, and onchain.",
      "slug": "demo",
      "amount": null,
      "currency": "USD",
      "imageUrl": "https://res.cloudinary.com/blockradar/image/upload/v1752049884/payment-links/ndlbgyb5wg70bpr3p1uu.png",
      "redirectUrl": null,
      "successMessage": null,
      "active": true,
      "inactiveMessage": null,
      "network": "mainnet",
      "type": "payment",
      "createdChannel": "dashboard",
      "metadata": {},
      "configurations": {},
      "createdAt": "2024-06-20T05:38:13.863Z",
      "updatedAt": "2025-07-09T08:31:25.328Z"
    },
    "toAsset": null,
    "toBlockchain": null,
    "toWallet": null
  }
}

Key Webhook Data Fields

The webhook payload includes comprehensive information about the payment:

Field	Description
`reference`	Custom reference from URL query parameters (e.g., ORDER123, customer ID)
`paymentLink`	Complete payment link details including name, description, and metadata
`asset`	Asset information (USDC, USDT, etc.) with network details
`blockchain`	Network information (Base, Ethereum, etc.)
`wallet`	Master wallet details and configurations
`address`	Customer address that received the payment
`amlScreening`	Anti-money laundering screening results
`assetSwept`	Auto-sweep status and details
`metadata`	Custom data from the payment link

The reference field in webhook payloads corresponds to the reference query parameter you include in the payment URL. This allows you to track payments back to specific orders, customers, or internal references in your system.

Best Practices

Security

Use HTTPS for all payment link sharing
Monitor webhook events for suspicious activity
Implement rate limiting on your webhook endpoints

User Experience

Clear descriptions of what the payment is for
Mobile-optimized payment pages
Multiple payment options when possible

Integration

Store payment link IDs for tracking
Use metadata to link payments to your systems
Implement webhook retry logic for reliability
Test webhooks in sandbox environment first

Use Cases & Examples

E-commerce Store

{
  "name": "Laptop Pro 2024",
  "description": "High-performance laptop with latest specifications",
  "amount": "299.99",
  "redirectUrl": "https://store.example.com/thank-you",
  "successMessage": "Thank you for your purchase! Your order has been confirmed.",
  "metadata": "{\"product_id\": \"laptop_pro_2024\", \"category\": \"electronics\", \"customer_email\": \"[email protected]\"}",
  "paymentLimit": 1
}

Service Invoice

{
  "name": "Web Development Services",
  "description": "Professional web development services - January 2024",
  "amount": "1500.00",
  "redirectUrl": "https://company.example.com/payment-success",
  "successMessage": "Payment received! We'll start working on your project immediately.",
  "metadata": "{\"invoice_id\": \"INV-2024-001\", \"service\": \"web_development\", \"client_id\": \"client_789\"}",
  "paymentLimit": 1
}

Donation Campaign

{
  "name": "Disaster Relief 2024",
  "description": "Support our disaster relief efforts in affected regions",
  "amount": "10.00",
  "redirectUrl": "https://charity.example.com/thank-you",
  "successMessage": "Thank you for your generous donation! Every contribution makes a difference.",
  "metadata": "{\"campaign\": \"disaster_relief_2024\", \"organization\": \"charity_foundation\", \"tax_deductible\": true}",
  "paymentLimit": 1000
}

Subscription Service

{
  "name": "Premium Plan Monthly",
  "description": "Monthly subscription to our premium service",
  "amount": "29.99",
  "redirectUrl": "https://service.example.com/welcome",
  "successMessage": "Welcome to Premium! Your subscription is now active.",
  "metadata": "{\"plan\": \"premium_monthly\", \"billing_cycle\": \"monthly\", \"features\": \"unlimited_access\"}",
  "paymentLimit": 100
}

These examples use the correct Blockradar payment links API parameters. The metadata field must be sent as a JSON string in form-data, and file uploads are supported for additional content.

Testing & Development

Sandbox Environment

Use testnet networks for development
Test webhook delivery and handling
Verify payment flows end-to-end
Test edge cases and error scenarios

Webhook Testing

Use tools like webhook.site for testing
Verify signature validation
Test retry mechanisms
Monitor webhook delivery rates

Checkout Plan

Blockradar Checkout is a programmable stablecoin payment layer for accepting onchain payments via links, embedded QR codes, and WalletConnect. Funds settle directly to your non-custodial wallets with built-in support for swap, bridge, and treasury routing.

Pricing

0.75% per transaction

Simple, transparent pricing with no monthly subscription costs.

Supported Stablecoins

USDC, USDT, cNGN, IDRX, EUROC, and more

Multi-Chain Support

Ethereum, Polygon, Base, Solana, Tron, Celo, and more

Treasury Management

Swap and Bridge: Convert and move assets across chains
Auto-settlement: Automatically settle to your preferred currency
Circle Gateway: Access Circle’s cross-chain transfer protocol
Auto-sweeping: Consolidate funds to your master wallet

This plan does not include Wallet-as-a-Service (WaaS) features or the provisioning of dedicated wallets for your end users.

Fetching Payment Link Transactions

You can retrieve all transactions associated with a specific payment link using the dedicated transactions endpoint. This is useful for:

Payment Tracking: Monitor all payments received through a specific link
Reconciliation: Match payments to orders or invoices
Reporting: Generate reports for specific payment links

Query Parameters

Parameter	Type	Description
`page`	number	Page number for pagination (default: 1)
`limit`	number	Number of results per page (default: 10)
`status`	string	Filter by transaction status (e.g., SUCCESS, PENDING, FAILED, INCOMPLETE)
`type`	string	Filter by transaction type (e.g., DEPOSIT)
`order`	string	Sort order (ASC or DESC)

Example Response

{
  "status": true,
  "message": "Transactions fetched successfully",
  "data": [
    {
      "id": "0d7a0b98-943c-48d0-8baa-216c29956050",
      "reference": "bjXPk7d00",
      "amount": "100.00",
      "amountUSD": "100.00",
      "status": "SUCCESS",
      "type": "DEPOSIT",
      "createdAt": "2025-01-15T10:30:00.000Z",
      "asset": {
        "symbol": "USDC",
        "name": "USD Coin"
      },
      "blockchain": {
        "name": "base",
        "slug": "base"
      },
      "customer": {
        "email": "[email protected]",
        "name": "John Doe"
      }
    }
  ],
  "meta": {
    "page": 1,
    "limit": 10,
    "total": 25,
    "totalPages": 3
  }
}

Support & Resources

API Reference

Getting Help

Email: [email protected]
API Reference: Checkout

Checkout and payment links are a powerful way to accept stablecoin payments with minimal integration effort. Start with simple use cases and gradually add complexity as you become more familiar with the system.

​Prerequisites

​Introduction

​How Payment Links Work

Creation

Sharing

Payment

Confirmation

​Payment Link Features

​Multi-Asset Support

​Flexible Configuration

​Security & Compliance

​Payment Flow

​1. Payment Link Creation

​2. Customer Pre-filling with Query Parameters

​3. Post-Payment Redirect

​4. Amount Configuration

​5. Payment Processing

​6. Transaction Response

​When the Amount Received Differs

​Underpaid Fixed-Amount Links

​Charging a Different Amount per Customer

​Try It Out

​Creating Payment Links

​Basic Payment Link

​Variable Amount Payment Link

​Payment Link with File Upload

​Payment Link Parameters

​Required Parameters

​Optional Parameters

​Payment Flow

​Customer Experience

​Merchant Experience

​Address Lifecycle

​Webhook Events

​Webhook Payload Example

​Key Webhook Data Fields

​Best Practices

​Security

​User Experience

​Integration

​Use Cases & Examples

​E-commerce Store

​Service Invoice

​Donation Campaign

​Subscription Service

​Testing & Development

​Sandbox Environment

​Webhook Testing

​Checkout Plan

​Pricing

0.75% per transaction

​Supported Stablecoins

​Multi-Chain Support

​Treasury Management

​Fetching Payment Link Transactions

​Query Parameters

​Example Response

​Support & Resources

​API Reference

​Getting Help

Prerequisites

Introduction

How Payment Links Work

Payment Link Features

Multi-Asset Support

Flexible Configuration

Security & Compliance

Payment Flow

1. Payment Link Creation

2. Customer Pre-filling with Query Parameters

3. Post-Payment Redirect

4. Amount Configuration

5. Payment Processing

6. Transaction Response

When the Amount Received Differs

Underpaid Fixed-Amount Links

Charging a Different Amount per Customer

Try It Out

Creating Payment Links

Basic Payment Link

Variable Amount Payment Link

Payment Link with File Upload

Payment Link Parameters

Required Parameters

Optional Parameters

Payment Flow

Customer Experience

Merchant Experience

Address Lifecycle

Webhook Events

Webhook Payload Example

Key Webhook Data Fields

Best Practices

Security

User Experience

Integration

Use Cases & Examples

E-commerce Store

Service Invoice

Donation Campaign

Subscription Service

Testing & Development

Sandbox Environment

Webhook Testing

Checkout Plan

Pricing

Supported Stablecoins

Multi-Chain Support

Treasury Management

Fetching Payment Link Transactions

Query Parameters

Example Response

Support & Resources

API Reference

Getting Help