Razorpay

Install corsair and @corsair-dev/razorpay, add the Razorpay plugin, and connect with an API key. Then call methods like corsair.razorpay.api.customers.create() from your app. Corsair verifies webhooks, and syncs data per tenant.

Yes. Razorpay requires an API key from your Razorpay account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Razorpay, GitHub, Notion, Stripe, and the rest. Trigger Razorpay from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for payment gateway for accepting online payments, subscriptions, and payouts in india. Common builds include sync jobs, admin tooling, and agents that call Razorpay APIs from your backend. Webhook handlers react to Razorpay events and fan out to Slack, email, or other plugins in the same tenant. Local DB entities let you query synced Razorpay records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Razorpay API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/razorpay in the open repo. When Razorpay ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Razorpay data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Razorpay data on your behalf.