Connect Razorpay and Make

In short

Connecting Razorpay to Make lets approved claims or commissions pay out automatically and be tracked to their final state. SBD built a QR cashback system for an industrial manufacturer using Make, Cloudflare Workers and Razorpay X payouts to UPI, so nobody processes payments by hand. Sales rose by 5 to 10%.

The workflows

What runs between Razorpay and Make.

Each line is one automated workflow. It shows the event in one tool, the checks and mapping in between, the action in the other tool and who is notified.

1. QR cashback for end users

   When

   A customer scans a QR code and submits the form

   Automation

   • Verify and validate
   • Map and normalise
   • Upsert by key

   Then

   Record the claim and check the code has not been used

   And

   • Audit log entry
   • Alert if it fails or goes quiet
   • Review queue if unsure

2. Partner commissions paid out

   When

   A claim passes the checks

   Automation

   • Verify and validate
   • Map and normalise
   • Upsert by key

   Then

   Create the payout through Razorpay with an idempotency key

   And

   • Audit log entry
   • Alert if it fails or goes quiet
   • Review queue if unsure

3. Refund batches

   When

   A payout webhook arrives

   Automation

   • Verify and validate
   • Map and normalise
   • Upsert by key

   Then

   Update the claim to processed, reversed or failed

   And

   • Audit log entry
   • Alert if it fails or goes quiet
   • Review queue if unsure

4. Distributor incentives

   When

   A payout fails or looks unusual

   Automation

   • Verify and validate
   • Map and normalise
   • Upsert by key

   Then

   Stop, alert a named person and hold it for review

   And

   • Audit log entry
   • Alert if it fails or goes quiet
   • Review queue if unsure

Every record passes through the same stages

1. 1Receive

   Webhook or polling from the source tool, with a signed payload and a replay log.

2. 2Validate

   We check required fields, types and the record key. Anything that fails goes to the review queue.

3. 3Map

   Fields are mapped to the destination schema, with dropdown values, currencies and dates normalised.

4. 4Upsert

   Each write is matched on the record key, so a retry updates the existing record.

5. 5Confirm

   The outcome is logged, an alert fires if the count stops moving, and a reconciliation runs each night.

Read this first

Where the simple setup breaks down.

A one-step Zap connects Razorpay and Make in an afternoon. This is what tends to go wrong once volume grows and edge cases appear.

• A retry can pay someone twice

  Automation platforms rerun failed scenarios, and a timeout does not prove the payment failed. Each payout needs an idempotency key, so a second attempt cannot send a second payment.

• Accepted is not the same as paid

  A payout passes through several states and can be reversed after looking successful. If you record it as paid when the API accepts it, your records drift from the bank. Webhooks have to update each payout to its final state.

• Bad details cost time and money

  A mistyped UPI ID or account fails or goes wrong. Validating the details at capture, before money is involved, saves the support work later.

• The same claim can arrive twice

  Customers rescan a QR code or submit a form again. Without a unique code and a check at the start, the scenario treats each attempt as a new claim.

What we wire up

The data flows.

1. 01
   When

   A customer scans a QR code and submits the form

   Then

   Record the claim and check the code has not been used

2. 02
   When

   A claim passes the checks

   Then

   Create the payout through Razorpay with an idempotency key

3. 03
   When

   A payout webhook arrives

   Then

   Update the claim to processed, reversed or failed

4. 04
   When

   A payout fails or looks unusual

   Then

   Stop, alert a named person and hold it for review

In every build

What every integration build includes.

Security and your data

Where the data goes, and who holds the keys.

Accounts

Every platform account is created in your name. We work through managed access you can revoke.

Credentials

Stored encrypted in the orchestration layer, scoped per connection and rotated at handover.

Data in transit

All traffic uses TLS, and webhooks are checked by signature before anything is processed.

Data at rest

We store only what the sync needs and keep no copies of your customer data on our machines.

AI steps

Where an integration uses a model, it is through a business API that does not train on your data.

Retention

Run logs are kept 90 days by default, which you can change. Card and ID numbers are redacted from payloads.

Agreements

DPA and NDA on request. Regional rules covered in our privacy policy.

Keys and sensitive data

How API keys, tokens and personal data are handled.

• Keys are kept in a vault

  API keys and tokens are stored in the orchestration layer's encrypted credential store or the platform's secret manager. None are written into workflows, repos, spreadsheets or chat.

• One credential per connection

  Each integration gets its own key, scoped to the objects and actions it needs. A lead sync cannot read invoices. Revoking one key stops one thing.

• Service accounts for connections

  Connections use a dedicated service user in your account, so nothing breaks when a person leaves and nothing runs under someone's name.

• Two-factor on every account

  Each platform account we set up has two-factor authentication on, and the recovery codes are handed to you.

• Rotation on handover and on request

  Keys are rotated when the build is handed over, when anyone with access leaves, and at any time you ask.

• Secrets are redacted from logs

  Audit logs redact tokens, card numbers, government IDs and anything you flag as sensitive before a line is written.

• Webhooks verified before processing

  Inbound calls are checked against the sending tool's signature. Unsigned or stale payloads are dropped and counted.

• Access you can see and revoke

  Our access is through managed roles in your accounts. You can see it, limit it or remove it without touching the build.

Engineering decisions

Decisions we make before writing the first workflow.

• Rate limits and backoff

  Each API has a ceiling, so calls are batched, queued and retried with increasing delays during busy periods.

• Backfill and pagination

  The first run loads history as well as new events. Backfills page through the source in order and resume after an interruption without writing a record twice.

• Out-of-order and duplicate events

  Webhooks can arrive twice or out of sequence. Each event carries a version or timestamp, so an older version cannot overwrite a newer one.

• Schema changes

  A renamed field or a new dropdown value is a common cause of silent failure. Payloads are checked against a contract, and a mismatch stops the run and raises a flag.

• Time zones, currencies, units

  Dates are stored in UTC and shown in local time. Amounts carry their currency and quantities their unit, and conversions happen once, in the map step.

• Sandbox first

  Builds run against sandbox or test accounts with seeded data first. Going live means switching credentials.

• Versioned and reversible

  Workflows and code are version-controlled. A release can be rolled back in minutes without losing the records processed since.

• API deprecations watched

  Tools retire API versions on a schedule. We track the dates for every connection in the runbook and upgrade before the cut-off.

• Cost per run known

  Each run logs its cost, including any model calls, so you can see spend as it builds up.

• Run metrics

  We chart runs per hour, records in and out, exception rate and latency, which often shows a problem before an alert fires.

Proof

Where we have done this.

• Customer story

  Automated cashback and loyalty system

  A QR cashback system for an industrial manufacturer with automated payouts through Razorpay X. Sales rose by 5 to 10%.

  Read the story →

Questions

What people ask about this pair.

Related

• +

  Shopify and QuickBooks

  Sales, fees and refunds posted so the books match each payout.

• +

  n8n and QuickBooks

  Bookkeeping workflows you can read, own and rerun, posting to the QuickBooks file your accountant trusts.

• +

  SmartSuite and Make

  SmartSuite holds the record, and Make sends changes to the other systems within the API quota.

• Solution

  Finance and accounting

  The workflows we automate for this kind of team.