UPI Payment Successful but Screenshot API Credits Are Missing: India Troubleshooting

If your UPI app says payment successful but screenshot API credits are missing, check the payment record and the API account as two separate things. A successful debit confirms what your payment app or bank recorded; it does not by itself prove the API provider’s account ledger was updated. Save the transaction reference, contact the provider through its official support channel, and ask it to reconcile the payment. If that does not resolve the issue, follow up with your bank or payment app and, if needed, NPCI.

This guide is for customers in India. The screenshot API provider and payment processor are not identified here, so the steps below do not assume a particular dashboard, ticket system, refund policy, or crediting time.

1. Confirm what happened to the UPI payment

Open the exact transaction in the UPI app you used. Check its final status, amount, date and time, and the merchant or payee name.
Compare those details with the bank account entry or debit SMS. If the app’s success screen and the transaction details or bank record disagree, rely on the detailed records and contact your bank or payment app for clarification.
Save the receipt and note the UPI transaction reference, transaction ID, or RRN. Keep the amount, transaction date and time, merchant name, and bank or payment app used together.
Check the API account for the relevant order or subscription and note the account email or ID and any invoice or order identifier you have.

NPCI says UPI users normally see a success message in BHIM and receive a bank SMS, although operator issues can delay confirmation. Its FAQ advises contacting your bank if confirmation has not arrived within an hour. It also describes cases where a successful transaction is delayed at the beneficiary bank and the funds may reach the beneficiary within 48 hours. Those statements concern UPI transaction confirmation and beneficiary-bank credit; they are not a promise that a software provider will add API credits within an hour or 48 hours. See the NPCI UPI FAQ.

2. Ask the screenshot API provider to reconcile the payment

Contact the provider using a support or billing channel you reach from its official website or account. Give it enough detail to find the transaction, and ask for a specific status: was the order marked paid by its payment processor, were credits applied, is the payment still being matched, or does the provider believe a refund is needed?

Account email or account ID
Order, invoice, or subscription identifier, if available
Amount, date and time, and merchant or payee name shown in the payment record
UPI transaction reference or RRN
Payment-app receipt or transaction details, shared through the provider’s official channel
A concise description: payment status shown by the app, whether the bank account was debited, and what is missing from the API account

Ask the provider to confirm whether credits were applied, are pending, or whether it will investigate a refund. Keep the support ticket or case reference and any replies. Do not assume that a missing balance will automatically be corrected or refunded by a particular deadline; the provider’s policy and payment flow are unknown.

3. Escalate through your bank, payment app, or NPCI

If the provider cannot locate the payment, or the payment status remains unclear, contact the bank or payment app you used. Explain that your account was debited but the merchant says it cannot find the payment, or that the API account was not credited. Ask what dispute or complaint route applies and retain the complaint reference.

Google Pay India’s guidance for a case where a merchant says it did not receive a payment is to contact the bank to file a chargeback. That is Google Pay’s published guidance for its users; it is not a guarantee that every bank or payment app follows the same process or that a chargeback will be granted. See Google Pay’s merchant-payment help.

You can also use the NPCI complaint portal to check transaction status in NPCI’s records and register a complaint routed to the relevant member institution. NPCI says that institution is responsible for resolving the complaint. The portal requests transaction information, including the bank, transaction date, and 12-digit transaction number or RRN; follow the current form instructions when filing. Keep both your NPCI reference and any bank or provider case numbers.

NPCI’s FAQ also says merchants can raise grievances or check UPI transaction status with their acquiring banks. That is a merchant-side route. As the customer, start with the API provider’s official billing or support channel and your own bank or payment app.

Keep your payment information safe

Share transaction details and receipts only through official provider, bank, payment-app, or NPCI channels.
Never share your UPI PIN or a one-time password with someone claiming to help. Support staff do not need those secrets to identify a transaction.
Do not send full payment credentials or approve an unexpected collect request as a way to receive a refund.
Keep copies of the receipt, relevant bank entry, provider messages, and every complaint or ticket reference until the issue is settled.

Choose the right route for each question

Contact	What it can check	What to provide
Screenshot API provider	Whether its order or account-credit record shows the payment and whether credits were applied	Account ID, order details, amount, timestamp, UPI reference or RRN, and receipt
Your bank or payment app	Your payer-side transaction record and the applicable complaint or dispute process	Transaction details, debit record, merchant response, and any provider ticket reference
NPCI complaint portal	Transaction status in NPCI’s records and routing a complaint to a member institution	Details requested by the current portal form, including bank, transaction date, and transaction number or RRN

Screenshot API alternative: ScreenshotNeo

If you are choosing a screenshot API after sorting out a payment issue, ScreenshotNeo is a website screenshot API and MCP server from Yorker Media. It provides PNG, JPEG, WebP, or PDF captures from a GET request. It accepts cookie and consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Only clean shots are billed: bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and the response reports the page verdict and billing status in headers. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.

Plans include 1,000 screenshots per month free with no card, Starter at $5 for 3,000, Growth at $15 for 15,000, Pro at $39 for 60,000, Scale at $99 for 250,000, and Business at $249 for 1,000,000. Yearly billing gives two months free, and every feature is on every plan. See the ScreenshotNeo documentation for the API and configuration options.

FAQ

Does a successful UPI status prove my API account received credits?

No. The UPI transaction record and the provider’s account-credit record are separate. Ask the provider to match the transaction to your order and confirm the credit status.

Should I wait 48 hours before contacting the provider?

NPCI’s 48-hour statement concerns a delayed payment reaching the beneficiary bank in certain cases. It is not an API crediting deadline. You can contact the provider with your transaction details while you check the payment status with your bank or app.

What if the provider says it cannot find the payment?

Ask it to confirm that it searched using the UPI reference or RRN, amount, date and time, and merchant details. Then contact your bank or payment app about the debit and applicable dispute route. You can also check transaction status and register a complaint through NPCI’s portal.

Can I send support my UPI PIN or OTP to prove the payment?

No. Keep your UPI PIN and OTP private. Share the receipt and transaction reference only through official support or payment channels.

Or skip the browser setup

ScreenshotNeo can return a website capture through one API call. See the ScreenshotNeo documentation for setup and options.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Cookie banners, popups, and chat widgets are removed before the shot.
Bot checks, blank pages, and failed loads are never billed.
An MCP server lets AI agents take screenshots.
1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000.