Inqud Docs
  • Developer
    • 🟒Inqud API
    • πŸ”‘Authentication
    • πŸͺWeb Hooks
      • Web Hook Verification
      • Payment Web Hook
    • Payment Statuses
    • πŸ“ƒAPI Reference
  • Payments
    • πŸ”’Payment Methods
    • πŸ’ΈWithdrawal/Payout
      • Cross Payout Feature
    • πŸ’°Deposit/Payin
    • πŸ’°H2H Deposit/Payin
  • Crypto Widget
    • πŸ’£Integration overview
    • Usage models
    • Extra features
      • Auto-conversion
      • Preselected currency checkout
    • πŸ’±Coverage
    • πŸ“„Glossary
    • βœ…Get started
      • Onboarding
      • Setup instructions
    • πŸ”ŽExplore
      • Checkouts
      • Requests
      • Payments
    • πŸ’»Integration
      • βš™οΈRedirect payment flow
      • βš™οΈEmbedded widget
      • βš™οΈUsing your own UI with Inqud processing
      • πŸͺWeb Hooks
        • Checkout Web Hook
        • Request Web Hook
      • πŸ“ƒAPI Reference
  • Crypto Static Addresses
    • πŸ“ƒOverview
    • πŸ’±Coverage
    • βœ…Get Started
      • 1️⃣Step 1. Account verification
      • 2️⃣Step 2. Project setup
      • 3️⃣Step 3. Integration
    • πŸ’»Integration
      • βš™οΈAPI Integration
      • πŸͺWeb Hooks
      • πŸ“ƒAPI Reference
  • Crypto Recurring
    • πŸ“ƒOverview
      • Inqud Hosted Page overview
      • Inqud Recurring SDK overview
    • πŸ’‘Use Cases
      • Subscription Payments
      • On-Demand Payments
    • πŸ’±Coverage
    • πŸ“„Glossary
    • βœ…Get Started
      • 1️⃣Step 1. Account verification
      • 2️⃣Step 2. Project setup
      • 3️⃣Step 3. Plan setup
      • 4️⃣Step 4. Integration
    • πŸ”ŽExplore
      • How it works
      • Project
      • Plan
      • Authorization
      • Subscription
      • Invoice
      • Payment Intent
    • πŸ’»Integration
      • βš™οΈInqud Hosted
      • βš™οΈRecurring SDK
        • SDK Package & Docs
        • SDK Usage Example
        • Example Sandbox
      • πŸͺWeb Hooks
        • Subscription Web Hook
        • Authorization Web Hook
        • Invoice Web Hook
      • πŸ“ƒAPI Reference
Powered by GitBook
On this page
  • Checkout flow
  • Checkout Types
  • Fixed Price Checkout
  • No Price Checkout
  • Predefined Amounts Checkout
  • Checkout Statuses
  • Check extra features:
  1. Crypto Widget
  2. Explore

Checkouts

PreviousExploreNextRequests

Last updated 16 days ago

Checkouts are specific to the and flows. In contrast, if you opt for an integration, the process involves only , with no checkouts.

Checkout constitutes a request from the merchant to the end user for the payment of a monetary amount, which can be optionally predefined, and is usually expressed in USD or other fiat currencies. In this process, the end user is granted the flexibility to choose the blockchain and cryptocurrency through which they wish to make the payment.

A checkout can be initiated by the merchant either through the Inqud API or manually via the app's user interface.

Checkout flow

After creating a Checkout, there are two methods available to present it to the end user:

  • Redirect: Direct your user to the Inqud Hosted page specifically designed for this purpose.

  • Widget: Embed the Inqud Widget on your website and initiate it by specifying the Checkout ID.

Integrate Redirect flow:

Integrate Widget to your website:

Checkout Types

Fixed Price Checkout: In this type, the merchant initiates a checkout by specifying the amount that the end-user is required to pay. This amount can be set in either fiat or cryptocurrencies.

No Price Checkout: For a No Price Checkout, the merchant sets up a checkout without specifying a particular amount. This approach allows the end user to pay an arbitrary amount, as long as it falls within the minimum and maximum limits established by Inqud.

Predefined Amount Checkout: For a Predefined Amount Checkout, the merchant sets up a checkout with specifying currency, several amount options too choose or allowing user to enter amount by himself. This approach allows the end user to choose from suggested options or pay an arbitrary amount, as long as it falls within the minimum and maximum limits established by Inqud.

Fixed Price Checkout

  1. Merchant Checkout Creation: The merchant sets up a checkout by specifying details: name, amount, and currency.

    • Example: "Apple iPhone 15 Pro (256 GB) - Black Titanium, 1399 USD."

  2. Checkout Display: The merchant then displays the created checkout on their website through the widget or provides a link to an Inqud hosted page for the checkout.

  3. User Selects Cryptocurrency: The end user views the checkout details and selects their preferred cryptocurrency for payment.

    • Example: The user chooses BTC.

  4. Inqud Calculates Approximate Amount: Inqud computes an approximate amount to be paid in the selected cryptocurrency.

    • Example: Approximately 0.037627 BTC.

  5. Payment Initiation: The end user clicks 'pay', and the Inqud widget displays the exact amount to be paid, the cryptocurrency type, the payment address, and a payment window timer.

    • Example: "0.037627 BTC to tb1qppgscyazkppucrqe7vvsha0zf7h68c2tmy6dwr, with a 60-minute window."

  6. User Completes Payment: The user sends the exact amount to the provided address.

  7. Transaction Registration and Status Update: Inqud registers the incoming transaction, conducts necessary checks, and updates the Checkout status accordingly.

  8. Notification to Merchant: Inqud notifies the merchant's system of any checkout status changes via a web hook.

  9. Final Status Display to User: The Inqud widget shows the final status to the end user. In a redirect flow, it displays a 'return to merchant website' button. If it’s an embedded widget, it executes the registered JavaScript callbacks.

No Price Checkout

  1. Merchant Checkout Creation: The merchant sets up a checkout by specifying details: name.

    • Example: "Game Balance Top Up"

  2. Checkout Display: The merchant then displays the created checkout on their website through the widget or provides a link to an Inqud hosted page for the checkout.

  3. User Selects Cryptocurrency: The end user views the checkout details and selects their preferred cryptocurrency for payment.

    • Example: The user chooses BTC.

  4. Inqud Shows Limits: Widget shows payment limits for selected crypto currency

    Example: Minimum 0.01 BTC, Maximum 1 BTC

Predefined Amounts Checkout

  1. Merchant Checkout Creation: The merchant sets up a checkout by specifying details: name.

    • Example: "Donation"

  2. Checkout Display: The merchant then displays the created checkout on their website through the widget or provides a link to an Inqud hosted page for the checkout.

  3. User Selects Cryptocurrency: The end user views the checkout details and selects their preferred cryptocurrency for payment.

    • Example: The user chooses BTC.

  4. Inqud Shows Limits: Widget shows payment limits for selected crypto currency

    Example: Minimum 0.01 BTC, Maximum 1 BTC

Checkout Statuses

NEW: This status is assigned when a Checkout is created, but the end user has not yet selected a preferred payment cryptocurrency.

REQUEST_CREATED: This status indicates that the user has chosen their preferred cryptocurrency for payment but has not yet initiated a blockchain transaction, or such a transaction has not been detected by the Inqud system.

PAYMENT_DETECTED: The user's payment has been made, and the transaction is detected but is still pending processing by the system.

EXPIRED: This status is used when the user either has not selected a preferred payment cryptocurrency or has not completed the payment, and the checkout expiration time has elapsed.

CONFLICT: This status arises when a user-initiated transaction is detected and processed, but issues are identified. These could be discrepancies in the payment amount or failures in compliance checks, such as Anti-Money Laundering (AML) regulations. For more specific details on the issue, a 'Reason' substatus is provided:

  • UNDERPAID: Indicates the user has paid less than the expected amount.

  • WRONG_CURRENCY: Indicates the user paid in wrong cryptocurrency.

  • OTHER: Covers various other potential issues with the payment that are not specifically categorized.

SUCCESS: This status denotes that the end user's transaction has been detected, successfully processed, and all requisite checks have been cleared. Moreover, the transaction amount meets the specifications of the request.

Check extra features:

πŸ”Ž
Embedded Widget
Inqud Hosted Page
API-only
requests
βš™οΈRedirect payment flow
βš™οΈEmbedded widget
Auto-conversion
Preselected currency