Skip to content

Payment integration

Connect Razorpay without treating checkout as proof

Connect Razorpay to Invoice Crowd for recoverable invoice checkout and signed, provider-reverified subscription events.

  • Status: Active
  • Verified against application docs
  • Provider terms still apply

Last updated:

Invoice Crowd Razorpay integration dashboard showing order recovery, captured payment verification and webhook readiness.

Configuration to settlement

How Razorpay fits the Invoice Crowd payment boundary

Connection, customer checkout and final settlement are separate stages. Read the status and limitations before showing the method on a live invoice.

Connect the merchant account

Credentials and mode stay tied to the selected business.

Invoice Crowd Razorpay connect razorpay illustration with fabricated sample data.

Enter only the fields the provider requires

Mode-matched API key, write-only API secret, dedicated webhook secret and Live/Test mode.

  • Selected business profile
  • Explicit live or test mode
  • Write-only secret editing

Confirm provider eligibility before rollout

Razorpay controls merchant onboarding, supported countries/currencies, fees and International Payments eligibility.

  • Merchant country and account
  • Invoice and settlement currency
  • Provider fees and review

Understand the customer path

Availability is evaluated before a customer enters checkout.

Invoice Crowd Razorpay customer checkout illustration with fabricated sample data.

Use the supported one-time flow

Invoice Crowd creates an immutable order attempt, verifies the Checkout signature, fetches payment and order state, and checks captured amount and currency.

  • Server-owned amount
  • Bound invoice allocation
  • Provider-controlled payment step

Read the recurring-payment boundary separately

Subscription events use a dedicated raw-body webhook secret, durable queue admission and authoritative provider re-fetch.

  • One-time and recurring differ
  • Existing bindings may be compatibility-only
  • Retired creators stay unavailable

Verify before recording money

The final local state follows provider evidence, not the browser.

Invoice Crowd Razorpay verify and record illustration with fabricated sample data.

Match the commercial record exactly

Signature, captured payment, paid order, tenant gateway, invoice allocation, amount, currency and event identity.

  • Merchant account and mode
  • Allocation, amount and currency
  • Successful provider state

Keep the current limitation visible

International or unsupported currency acceptance can depend on the merchant account being enabled by Razorpay. Ambiguous creates remain locked for recovery rather than being repeated.

  • No inferred settlement
  • Pending stays pending
  • Mismatch fails closed

Integration facts

What to verify before using Razorpay

The fields below describe the current Invoice Crowd path; the provider remains the source for merchant eligibility, fees and regional availability.

  • Availability

    Active

  • One-time payment

    Invoice Crowd creates an immutable order attempt, verifies the Checkout signature, fetches payment and order state, and checks captured amount and currency.

  • Recurring payments

    Subscription events use a dedicated raw-body webhook secret, durable queue admission and authoritative provider re-fetch.

  • Merchant setup

    Mode-matched API key, write-only API secret, dedicated webhook secret and Live/Test mode.

  • Settlement evidence

    Signature, captured payment, paid order, tenant gateway, invoice allocation, amount, currency and event identity.

  • Regional fit

    Razorpay controls merchant onboarding, supported countries/currencies, fees and International Payments eligibility.

  • Current boundary

    International or unsupported currency acceptance can depend on the merchant account being enabled by Razorpay. Ambiguous creates remain locked for recovery rather than being repeated.

  • Invoice data

    Amount, currency and allocation are derived from the current server-side invoice state.

  • Customer result

    A provider screen or browser return is a locator, not sufficient settlement proof.

  • Retries

    Durable attempts and stable provider identities prevent an uncertain response from becoming an unbounded duplicate payment.

  • Provider fees

    Gateway fees, exchange costs and settlement timing come from the merchant agreement, not the Invoice Crowd subscription.

  • Alternative gateways

    Configure another active provider when this gateway does not support the merchant, customer, currency or collection model.

Questions

Razorpay and Invoice Crowd, answered

Is the Razorpay integration currently available in Invoice Crowd?

Current status: Active. Invoice Crowd creates an immutable order attempt, verifies the Checkout signature, fetches payment and order state, and checks captured amount and currency.

What do I need to connect Razorpay?

Mode-matched API key, write-only API secret, dedicated webhook secret and Live/Test mode. Razorpay controls merchant onboarding, supported countries/currencies, fees and International Payments eligibility.

How does Razorpay one-time checkout work?

Invoice Crowd creates an immutable order attempt, verifies the Checkout signature, fetches payment and order state, and checks captured amount and currency.

Does Razorpay support recurring payments in Invoice Crowd?

Subscription events use a dedicated raw-body webhook secret, durable queue admission and authoritative provider re-fetch.

How does Invoice Crowd decide that a payment succeeded?

Signature, captured payment, paid order, tenant gateway, invoice allocation, amount, currency and event identity. A browser return or posted status alone cannot settle the invoice.

Are gateway fees included in Invoice Crowd pricing?

No. Provider transaction fees, foreign-exchange costs, settlement timing and account terms are controlled by the gateway and merchant agreement. Check the provider before activation.

Test Razorpay with a representative invoice

Start with sandbox or test mode where the provider offers it, verify the exact currency and payment result, then plan production activation.

  • No browser-only settlement
  • Provider terms apply
  • Current status is visible