daysTime to key
NoNo-human path
3Human gates
3/10Onboarding score
KYC / business checkManual reviewPhone OTP
Fastest path to a key
- Phone OTPRegister at business.phonepe.com/pg/register with mobile number + OTP
- Enter business details: PAN, business type, GSTIN (if applicable), bank account, website/app URL
- Phone OTPOpen PhonePe Business Dashboard > Developer Settings and copy the Client ID + Client Secret (+ client_version)
- Phone OTPPOST client credentials to the token endpoint: UAT https://api-preprod.phonepe.com/apis/pg-sandbox/v1/oauth/token, prod https://api.phonepe.com/apis/identity-manager/v1/oauth/token. This returns an O-Bearer access_tok…
- Phone OTPTest in the UAT sandbox using templates, test cards and mock OTP 123456
- KYC / business checkGo-live: KYC documents reviewed + website compliance check by PhonePe before production transactions
- Working API key
Biggest gap
No agent surface at all: no MCP, no machine-readable docs, and an unclear path to test credentials without a KYC'd merchant account
Worth copying
A sandbox with configurable response templates (success/failure/pending) lets an agent test every payment branch deterministically
Sources (5) · checked 2026-10-11
- https://developer.phonepe.com/payment-gateway
- https://developer.phonepe.com/payment-gateway/website-integration/standard-checkout/api-integration/api-reference/authorization
- https://developer.phonepe.com/payment-gateway/uat-testing-go-live/uat-sandbox
- https://business.phonepe.com/pg/register
- https://inc42.com/?p=520462
33Readiness score / 100
L1 Agent-readableBeats 42% of 1,846 companies
Access20/20
Context3/20
Interfaces8/32
Onboarding0/19
Trust2/9
Biggest gains
- +12 Remote MCP server for the product. Host a remote MCP server (e.g. mcp.<domain>/mcp, Streamable HTTP) for your core actions.
- +8 llms.txt exists. Publish /llms.txt: a markdown index of your docs at the root or docs host.
- +8 Machine-readable API spec. Publish an OpenAPI spec at a stable URL like /openapi.json and link it from llms.txt.
All 20 checks
- PASSAgents get the real page, not a bot wall10
- PASSrobots.txt lets user-triggered agents in6
- PASSContent is server-rendered4
- FAILllms.txt exists8
- FAILllms-full.txt exists3
- FAILDocs available as markdown6
- PASSSitemap2
- PASSStructured metadata1
- PASSPublic developer docs4
- FAILMachine-readable API spec8
- FAILRemote MCP server for the product12
- FAILDocs MCP or searchable docs4
- PASSSDKs and a CLI4
- FAILOAuth discovery metadata5
- FAILAgents can self-register OAuth clients6
- FAILSelf-serve API keys5
- FAILFree tier or test mode3
- FAILAgent manifests4
- PASSsecurity.txt2
- FAILPublic status page3
Your fix pack: 13 changes, up to +67 points
Each change is ready to paste, filled in for phonepe.com, with a command to check it worked. Or hand the whole list to your coding agent.
Want the full treatment, not just these fixes? Get the prompt that takes your coding agent through every phase.
Add the badge to your README
[](https://agentsready.dev/c/phonepe.com)