LogoLogo
  • Introduction
  • Overview
    • What are cryptocurrencies
    • Why accept crypto
    • Our products
      • Payment Gateway
      • Earnings on deposit
      • Manual Invoices
      • Payment & Donation button
      • White Label
      • Affiliate program
      • Demo Shop
  • Getting started
    • Basics
      • What is an Invoice?
      • Accepting Payments
      • Withdrawing Your Funds from OMY Payments
      • Security and Transparency
  • API
    • Overview
    • Authentication
    • API Endpoints
      • Get Merchant Assets
      • Create Invoice
      • Create Invoice by Crypto
      • Get Invoice Data
      • Withdraw Asset
    • Callbacks
    • Common issues
  • No-code Integration
    • Overview
    • Getting Started with No‑Code Integration
  • How to Create Payment Links
  • Advanced Use Cases and Best Practices for No‑Code Integration
  • Legal
    • Terms of Use
Powered by GitBook
On this page

How to Create Payment Links

Payment links allow you to generate a dedicated payment page without writing any code. Even though Omypayments does not offer its own no‑code widget, you can easily set up payment links using third‑party no‑code tools.

How It Works:

  • Dynamic Invoice Generation: A no‑code workflow (via Zapier, for example) sends a request to the Omypayments API to create an invoice. The API generates a payment link with hidden parameters (like the invoice amount).

  • User Interface: The generated payment link directs customers to a payment page displaying a prominent “Pay” button. Hidden fields (containing invoice details) ensure the correct amount is processed.

  • Behind the Scenes: When the customer clicks “Pay,” the hidden parameters are submitted, and the system validates the data before processing the payment.

Example Workflow:

  1. Trigger: A customer clicks a “Pay” button on your website.

  2. Invoice Creation: A Zapier workflow creates an invoice via the Omypayments API.

  3. Link Generation: The API returns a payment link with hidden parameters (e.g., amount).

  4. Payment Page: The customer is directed to the payment page and completes the payment.

  5. Confirmation: The system updates the invoice status and sends a callback to your endpoint.

PreviousGetting Started with No‑Code IntegrationNextAdvanced Use Cases and Best Practices for No‑Code Integration

Last updated 2 months ago