In Make, start a scenario with Razorpay’s Watch Payment Captured trigger, select a trusted page URL associated with the order, then use an HTTP request to call a screenshot API. For production, account for webhook verification, duplicate and out-of-order events, and where the returned image will be stored. If you use Razorpay’s Custom webhook route, first confirm that your configuration can verify Razorpay’s signature over the raw request body.
Choose how the payment event reaches Make
There are two ways to start the workflow. Choose based on what your Make connection exposes and how you will verify incoming events—not just on which route takes fewer clicks.
As an Amazon Associate I earn from qualifying purchases.
| Trigger design | How it works | Important consideration |
|---|---|---|
| Make’s Razorpay Watch Payment Captured | Connect Razorpay in Make and use the trigger for a newly captured payment. Make describes it as triggering when a payment is successfully captured. | Make manages the trigger connection. Check which event fields the module actually supplies and whether they are enough to identify the order and the page to capture. |
| Razorpay webhook to Make Custom webhook | Create a Custom webhook in Make, then configure Razorpay to send the relevant event to its URL. | Do not assume this route can meet Razorpay’s raw-body signature verification requirement. Establish whether your exact configuration exposes the original request body and headers and permits the required verification before sending production traffic. |
Use a captured-payment event when the screenshot should happen only after a successful capture. A payment event payload is a snapshot: Razorpay notes that a payment may already be captured when payment.authorized fires, while that event’s payload still contains authorization-time details. Do not infer that an older event represents the current payment state.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Build the Make scenario
- Create a scenario. In Make, add the Razorpay Watch Payment Captured trigger and connect your Razorpay account. If you are using Razorpay’s outbound webhook instead, add a Webhooks > Custom webhook trigger and configure Razorpay to send the event to the generated URL.
- Capture a test event. Run the scenario’s listening/test mode and use a non-production payment or other safe test arrangement. Inspect the actual fields Make receives; do not assume the event contains a page URL or that similarly named fields have the same meaning across event types.
- Choose the target page safely. Prefer a URL constructed from a trusted order identifier or selected from an allowlist. If the page URL is stored with order data, use it only after validating its host and path. Do not send an arbitrary URL from untrusted event data to a screenshot service: that can expose internal services or data accessible from the capture environment.
- Add the screenshot request. Add Make’s HTTP Make a request module after the trigger. Configure it to call the screenshot API over HTTPS, supply the target URL and credentials as required by that API, and keep the key in a protected connection or secret field rather than hard-coding it in a public page or scenario output.
- Handle the response. Decide whether the scenario should receive the image itself or a result containing a file URL. Connect a storage or internal-record destination that your organization has chosen; the screenshot API documentation does not determine which destination is appropriate for you.
- Make processing safe to retry. Record the Razorpay event ID and make downstream effects idempotent, so a redelivery does not create repeated records or trigger repeated business actions. Add error handling for unsuccessful screenshot requests and destination failures.
Choose synchronous or asynchronous capture
Synchronous request
A synchronous capture returns the screenshot as the HTTP request result, which suits a short flow where Make can pass the response to the next module. Confirm how your chosen API returns image data and how the destination module accepts it; do not assume an image response is automatically a shareable file URL.
#1 Best Overall
- Use the, easy-to-use, and customizable POS to get started.
- Accept contactless payments, chip cards, Apple Pay, and Google Pay from anywhere, with improved connectivity, extended battery life, and enhanced security. Pay one low rate for every tap or dip.
- No long-term commitments or contracts, no monthly fees- and with offline payments, keep taking payments for up to 24 hours.
- Safely and securely accepts payments anywhere. Plus, get data security, 24/7 fraud prevention, and payment-dispute management at no extra cost.
- Use the, easy-to-use, and customizable POS to get started.
Asynchronous request with a callback
ScreenshotOne documents asynchronous capture using async=true and response_type=json, with options for storage and a webhook_url callback. When the result needs to include the stored file location, its documentation specifies storage_return_location=true. Its callback example can include a screenshot URL and, when configured, a storage location. This design separates the initial payment-triggered scenario from waiting for rendering, but requires a second Make webhook path to receive the result.
ScreenshotOne also documents webhook_errors=true for receiving error details. Validate asynchronous callback signatures using its separate signing key and the documented X-ScreenshotOne-Signature header before trusting the result. Keep the API key and signing key private; they have different roles.
Rank #2
- Get your money as soon as the next business day.
- Get set up quickly with no long-term commitments. Download the Square Point of Sale app for free, create an account, and start taking payments anywhere.
- Run your business all in one place with the free Square Point of Sale app. Track your sales, manage inventory, accept tips, send receipts digitally, and more.
- Works with Apple devices with a Lightning connector.
Set the capture behavior for the page
Use only options that solve a specific page or workflow need. For a payment confirmation or order page, confirm that the capture represents the right customer and order, and avoid storing sensitive payment data in the image unless your handling policy allows it.
- Page readiness: Wait for a known selector, a delay, or network idle when the page needs time to render. Prefer a meaningful page-ready condition over a long fixed delay where the service supports it.
- Page scope: Choose full-page capture for a complete record or a CSS selector when only a specific receipt, confirmation, or report section is needed.
- Authentication: If the page is private, use supported cookies, custom headers, or authorization carefully. Treat those credentials as secrets, and restrict which host can receive them.
- Output and rendering: Choose an image format or PDF to match the archive or downstream system. Consider viewport, device preset, dark mode, and retina scale if the page’s appearance depends on them.
- Page cleanup: Use supported CSS or JavaScript, click actions, or selector hiding only when the page requires them. Blocking requests or resource types can speed rendering, but may also prevent needed content from appearing.
- Repeat work: Caching, asynchronous jobs, bulk capture, and signed delivery links are relevant only if they fit the event volume, freshness, and access-control requirements of your workflow.
Verify webhook security and delivery behavior
Razorpay signs webhook requests with HMAC-SHA256 using the configured webhook secret. Its validation instructions require calculating the signature over the raw request body; parsing or casting the body first changes what is signed. Razorpay also provides x-razorpay-event-id to identify duplicate events.
Rank #3
- With Square Terminal, you can ring up sales, accept payments, and print receipts, all with one device. Use it at the counter or ring up customers anywhere in your store.
- Accept all major credit and debit cards and pay one low rate with no hidden fees and no long-term contracts.
- Process chip cards in just two seconds.
- Get your money as soon as the next business day.
- Use it cordlessly with the built-in battery, designed to last all day.
The reviewed Make documentation establishes that Custom webhooks exist, but does not establish that every Make-only configuration exposes the raw body in a form suitable for that signature check. Before relying on a direct Razorpay-to-Make connection in production, demonstrate that your exact setup validates the signature correctly. If it cannot, put a small verification endpoint in front of Make: it should validate the signature against the unchanged raw body, reject invalid requests, and forward only verified event data.
Razorpay may retry failed deliveries with exponential backoff for 24 hours after event creation, and events may not arrive in order. Make Custom webhooks can queue calls that are not processed immediately. Design the workflow around those conditions: deduplicate by event ID, make side effects idempotent, and avoid assuming that arrival order equals payment order.
Rank #4
- Pay one transparent rate per swipe for Visa, Mastercard, Discover and American Express.
- Works in conjunction with most downloadable Square point-of-sale apps on your device. Customers can pay, tip and sign directly on your device. Track payments in cash, gift cards and more. Also lets you send receipts via e-mail or text message, makes it easy to apply discounts, keeps a data and sales history log and more.
- Accepts magstripe credit card payments, including those from Visa, Mastercard, Discover and American Express (fees apply).
- App sends deposits to your bank account within 1 to 2 business days, or enjoy instant deposits (fees apply).
Troubleshoot common failures
| Symptom | Likely cause | What to check or change |
|---|---|---|
| No scenario execution | The trigger is not listening, the selected event is not the one being sent, or Razorpay is posting to a different webhook URL. | Check the trigger’s listening state and the configured event and destination URL. Test with a safe event and inspect Make’s received bundle. |
| Signature validation fails | The body was parsed or transformed before verification, the wrong secret was used, or the request bytes differ from the signed body. | Verify the signature over the exact raw body using the webhook secret configured in Razorpay. If Make cannot provide that body unchanged, verify upstream before forwarding to Make. |
| The same payment runs more than once | Razorpay redelivered an event or the scenario retried work after a partial failure. | Persist the event ID and check it before side effects. Make the record creation and other downstream actions safe to repeat. |
| The wrong page is captured | The workflow used a stale event snapshot, an incorrect order-to-URL association, or an unvalidated URL. | Use the captured-payment event when capture is the condition; resolve the target from trusted order data and validate the permitted host and path. |
| The screenshot is blank or incomplete | The page was not ready, the selected content is lazy-loaded, authentication was missing, or request blocking removed required resources. | Wait for a page-specific selector or suitable readiness condition, check authentication and viewport settings, and relax blocking rules that affect required content. |
| Make receives no usable file | The API returned image bytes where a later module expects a URL, or an asynchronous job has not delivered its result yet. | Match the request mode to the next module’s input. For asynchronous capture, receive the callback and use the returned result fields; configure storage if the workflow needs a stored location. |
| Credentials appear in logs or output | A key was put into a public URL, page, or logged field rather than a protected secret setting. | Move credentials to protected configuration, limit access to scenario runs and logs, and rotate any credential that was exposed. |
Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server. Its API can return a screenshot or PDF from one GET request; in Make, configure the HTTP request with your access key and the validated target URL. Use ScreenshotNeo when you want cookie banners accepted and removed along with 60+ known consent platforms, newsletter popups, and chat widgets before capture; those cleanup steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status in headers. AI agents can also use its MCP server and the take_screenshot, get_page_info, and capture_pdf tools.
Example cURL request (replace the target with the page you have safely selected):
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for the request options. In Make, map the validated target URL and protected API key into the equivalent HTTPS GET request; do not pass an untrusted event URL directly.
Best Value
- Accept all major credit and debit cards and pay one low rate
- No hidden fees and no long-term contracts
- Mobile card reader that accepts payments anywhere & anytime
- Use the free SumUp App on your smartphone or tablet to start accepting transactions
- Simply pay 2.6% +10 per in-person transaction
ScreenshotNeo includes 1,000 screenshots per month free with no card, and paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
