STEP 1
Connect Checkout and Razorpay
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Checkout and Razorpay Integration
Connect Checkout and Razorpay to automate finance workflows. Trigger events from one app, run actions in the other and use AI to make smart decisions. Integrate apps in 3 simple steps - no code required.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about Checkout and Razorpay
Detailed info you need to know about Checkout and Razorpay integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Checkout to Razorpay
Set up your Checkout and Razorpay integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Checkout and Razorpay nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between Checkout and Razorpay. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Checkout and Razorpay work in WEXTL?
WEXTL exposes actions and triggers for Checkout and Razorpay that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
Checkout triggersRazorpay actions
Checkout modules
- Accept a DisputeAccepts liability for a dispute.
- Activate a CardActivates an issued card.
- Anonymize an ApplicantAnonymizes applicant personal data.
- Capture a PaymentCaptures an authorized payment.
- Create a CardIssues a new card.
- Create a CardholderCreates an issuing cardholder.
- Create a CustomerAdds a new customer.
- Create an ApplicantCreates an onboarding applicant in the system.
- Create a PaymentRequests a payment or payout.
- Create a Payment LinkGenerates a hosted payment link.
- Create a TransferMoves funds between accounts.
- Delete a CustomerRemoves a customer from the system.
- Enroll a Card in 3DSBegins the 3DS enrollment process for a card.
- Get 3DS EnrollmentRetrieves the 3DS enrollment status of a card.
- Get a CardRetrieves the details of a card.
- Get a CardholderRetrieves cardholder details from the service.
- Get a CustomerRetrieves customer details.
- Get a DisputeRetrieves a dispute.
- Get a File's InfoRetrieves uploaded file information.
- Get an ApplicantRetrieves applicant details.
- Get a PaymentFetches a specific payment.
- Get a Payment LinkRetrieves a payment link from the service.
- Get a TransactionRetrieves a transaction based on the specified criteria.
- Get a TransferRetrieves details of a transfer.
- Get Dispute EvidenceRetrieves evidence that has been submitted for a dispute.
- Get DisputesRetrieves all disputes.
- Get Entity BalancesChecks currency balances for a specific entity.
- Get Payment ActionsRetrieves actions performed on a payment.
- Get PaymentsRetrieves all payments.
- Get TransactionsRetrieves all issuing transactions.
- Increment AuthorizationIncreases the authorization amount for a transaction.
- Make an API CallPerforms an arbitrary authorized API call.
- Provide Dispute EvidenceUploads evidence for a dispute.
- Refund a PaymentIssues a refund for a specific payment.
- Reverse a PaymentReverses a payment transaction.
- Submit EvidenceSubmits dispute evidence for review.
- Update a CardholderUpdates cardholder information.
- Update a CustomerModifies customer information.
- Update an ApplicantModifies applicant information in the system.
- Update Card DetailsModifies card details for a specific card.
- Upload a FileUploads a file for disputes or verification.
- Void a PaymentVoids an existing payment in the system.
- Watch DisputesTriggers when a new dispute is recorded or an existing dispute is updated.
- Watch PaymentsTriggers when a new payment is registered.
- Watch TransactionsTriggers when new transactions are recorded.
Razorpay modules
- Accept a DisputeAccepts a dispute and closes it in the customer's favour.
- Add a Customer Bank AccountAdds a bank account to a customer.
- Add an Allowed PayerAdds a bank account that is allowed to pay a TPV customer identifier.
- Add a Receiver to a Customer IdentifierAdds a VPA or bank receiver to a customer identifier.
- Cancel a Customer TokenCancels a saved payment token.
- Cancel an InvoiceCancels an issued invoice.
- Cancel a Payment LinkCancels a payment link so it can no longer be paid.
- Cancel a Scheduled Subscription ChangeCancels a pending update on a subscription.
- Cancel a SubscriptionCancels a subscription.
- Capture a PaymentCaptures an authorised payment.
- Close a Customer IdentifierCloses a customer identifier so it stops receiving transfers.
- Close a QR CodeCloses a QR code so it stops accepting payments.
- Contest a DisputeSubmits evidence to contest a dispute.
- Create a Beta AccountCreates a Route account on the published beta accounts API.
- Create a CustomerCreates a customer record in the account.
- Create a Customer IdentifierCreates a customer identifier that can receive bank or UPI transfers.
- Create a DocumentUploads a document used as dispute evidence.
- Create a Linked AccountCreates a Route linked account.
- Create an Authorisation LinkCreates a link the customer uses to authorise a recurring mandate.
- Create an Instant SettlementCreates an on-demand settlement of the available balance.
- Create an InvoiceCreates an invoice for a customer.
- Create an ItemCreates a reusable invoice line item.
- Create an OrderCreates an order for one payment attempt.
- Create a Payment LinkCreates a payment link the customer can open and pay.
- Create a PlanCreates a subscription billing plan.
- Create a QR CodeCreates a QR code the customer can pay.
- Create a Recurring PaymentCharges a saved token for a subsequent recurring payment.
- Create a RefundRefunds a payment in full or in part.
- Create a SubscriptionCreates a subscription on a billing plan.
- Create a Subscription Add-onAdds a one-time charge to a subscription.
- Create a TransferCreates a direct transfer to a linked account.
- Create Transfers from a PaymentSplits a captured payment across linked accounts.
- Delete a Customer Bank AccountRemoves a bank account from a customer.
- Delete a Customer TokenDeletes a saved payment token.
- Delete an Add-onDeletes a subscription add-on.
- Delete an Allowed PayerRemoves an allowed payer from a TPV customer identifier.
- Delete an InvoiceDeletes a draft invoice.
- Delete an ItemDeletes a line item.
- Delete an Offer from a SubscriptionRemoves an offer linked to a subscription.
- Fetch Payment MethodsReturns the banks Razorpay supports for recurring payment methods.
- Get a Bank Transfer PaymentReturns the bank-transfer details of a Smart Collect payment.
- Get a Beta AccountReturns one Route account from the published beta accounts API.
- Get a Card FingerprintReturns the card reference for a saved token or tokenised number.
- Get a CustomerReturns a single customer.
- Get a Customer IdentifierReturns a single customer identifier.
- Get a Customer TokenReturns a single saved payment token.
- Get a DisputeReturns a single dispute.
- Get a DocumentReturns document information.
- Get a Linked AccountReturns a single linked account.
- Get an Add-onReturns a single subscription add-on.
Explore alternative integrations
There are other apps [9] supported by WEXTL that can be paired with Checkout and Razorpay integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting Checkout and Razorpay.
Connect your Checkout and Razorpay accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when Checkout's "Watch Disputes" fires, WEXTL can "Accept a Dispute" in Razorpay. Checkout has 3 triggers (including Watch Disputes, Watch Payments, and Watch Transactions); Razorpay has 115 actions (including Accept a Dispute, Add a Customer Bank Account, and Add an Allowed Payer). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. Checkout-to-Razorpay automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment Checkout (or Razorpay) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your Checkout + Razorpay automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the Checkout and Razorpay integration.
- Checkout and Razorpay integration source code, module specs and credentials implementation.
- Our Checkout and Razorpay integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Checkout and Razorpay — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- Checkout integration information
- Razorpay integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library