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
  • Prerequisites
  • Setting up Web Hook
  • Checkout statuses
  • Notification
  1. Crypto Widget
  2. Integration
  3. Web Hooks

Checkout Web Hook

PreviousWeb HooksNextRequest Web Hook

Last updated 3 months ago

The Checkout webhook is essential for integrations that utilize the or options.

For foundational information on webhooks, including key concepts and verification methods, please refer to the page.

Checkout Web Hooks enable merchant systems to receive timely notifications regarding status changes of Checkouts.

Learn more about checkouts:

Prerequisites

  • Your business account with Inqud is set up.

  • The Crypto Widget has been established and configured within the Inqud platform.

  • The Crypto Widget is active.

Setting up Web Hook

  1. Open the and sign in.

  2. From the left menu bar, choose "Crypto widgets".

  3. Select the desired widget.

  4. Open "Webhooks"

  5. Locate the "Checkout webhook" option and click on "Add".

  6. Enter the required details:

    • Webhook link: Provide the URL of your webserver that will handle the callbacks.

    • Webhook secret: Enter a secret key for signature calculation (optional).

  7. Click on "Save" to finalize your settings.

Checkout statuses

Notification

The Checkout Web Hook activates with every transition in checkout status. It requires your web server to respond with a 200 status code. If a different status code is returned, the Web Hook will attempt retries multiple times, using an exponential back-off strategy.

For detailed request specifications, please refer to the following page:

Visit the to learn more about the various checkout statuses.

(see Callbacks sections)

💻
🪝
Inqud Hosted
Embedded Widget
Webhook Basics
Checkouts
app
Checkout Web Hook Specification
Checkouts page