DOCSEARCHbyAlgolia
Submit Docs

Nimbbl Documentation

website·Indexed 32 days ago

https://docs.nimbbl.tech

A payment orchestration platform for Indian merchants. Documentation includes integration guides, product details, and Command Center instructions, as well as test credentials and activation for go-live.

Tokens
923
Snippets
0
Records
10
Agent score
57%

What's inside Nimbbl

  1. Collect payments using Nimbbl Plug and Play (No-Code)

    Nimbbl provides a 'Plug and Play' suite of no-code tools for merchants to collect payments without writing custom code. This includes plugins for popular eCommerce platforms (WooCommerce, Magento, Shopify, Wix, and OpenCart), shareable Payment Links, and branded hosted Payment Pages.

  2. Nimbbl Product Suite Overview

    Nimbbl is a payment orchestration platform for Indian merchants offering four primary product modules:

    • Sonic: A one-click checkout solution designed to reduce customer drop-offs.
    • Orbit: A payment processing engine supporting 25+ gateways, multi-currency transactions, and PCI DSS Level 1 compliance.
    • Pulse: A smart routing engine providing rule-based and ML-based dynamic routing with automatic fallback and recovery logic.
    • Boostr: An affordability and offers engine managing personalization, EMI, BNPL (Buy Now Pay Later), and customer incentives.

  3. Manage Payments and API Keys via Nimbbl Command Center

    The Command Center is the unified dashboard for managing Nimbbl operations. Key capabilities include:

    • Search & Operations: Filter and act on Orders, Payments, Refunds, Captures (pre-authorizations), and Voids.
    • Resource Creation: Generate Payment Links, Payment Pages, and configure Offers (including payment mode targeting and eligibility rules) and Subventions for EMI.
    • Developer Settings: Manage API access keys (Credentials) and configure Payment Partner gateway settings.
    • Analytics: Access payment reporting and performance analytics.

  4. Create and manage Nimbbl Payment Links

    Payment Links allow merchants to generate shareable URLs that customers can use to complete payments. The functionality includes creating links, managing existing links, configuring webhooks for payment notifications, and a specific field reference for link parameters.

  5. Implement Standard Checkout (Low-Code SDK)

    The Standard Checkout integration follows a specific workflow:

    1. Order Creation: Create the order on the server-side.
    2. Client SDK Setup: Integrate the appropriate SDK for the platform (JavaScript for Web, Native Android/iOS, React Native, Flutter, or Mobile WebView).
    3. Post-Payment Handling:
      • Validate the payment response using HMAC signature verification.
      • Process refunds via server-side calls.
      • Use webhooks or transaction enquiry polling to keep the system state updated.

  6. Nimbbl Integration Path Options

    Nimbbl provides three primary integration paths depending on the level of control and development effort required:

    • No-Code (Plug and Play): Fastest deployment with minimal technical setup.
    • Low-Code (Standard Checkout): Uses SDKs (Web, Android, iOS, React Native, Flutter) to handle the checkout UI while maintaining server-side order control.
    • Full API: Complete control over the payment experience via direct API integration.

  7. Set up branded Nimbbl Payment Pages

    Payment Pages are branded, hosted checkout pages provided by Nimbbl. Merchants can create these pages, manage them, and utilize custom fields to collect additional information from customers during the checkout process.

  8. Handle Payment Notifications via Webhooks and Callbacks

    Nimbbl uses two primary mechanisms to communicate transaction results:

    • Webhooks: Server-to-server asynchronous notifications. Available for Payment events (Authorization, Capture, Void), Refund events (success, failed, pending), and Payment Link lifecycle events. Version 4 includes updated envelopes and signatures.
    • Callbacks: Synchronous responses delivered after a transaction. This includes the payment-callback (delivered to the server's callback_url) and the checkout-callback (delivered to the browser via the Sonic SDK).

  10. Use Nimbbl Server Kits for backend integration

    Nimbbl provides Server Kits (Backend SDKs) to simplify server-side integration. Official SDKs are available for PHP and .NET.