AtlasPayment MethodsPhonePe

PhonePe

pmt_phonepe

Introduced in 2015, PhonePe is a digital wallet or mobile payment service for consumer and merchant payments.

Wallet
Use cases:
Channels:
Initiation:
Users
600M
Markets
1
TPV
$1.7T
Transactions
120B

Number of Users

UsersYoY
20222023202420252026Five-year Users and YoY data will appear here

Total Payment Volume

TPVYoY
20222023202420252026Five-year TPV and YoY data will appear here

Markets

Markets and currencies connected to PhonePe across consumer, processing and settlement flows.

Market
IndiaAPAC$1.8T120B339M

Capabilities

How PhonePe works across its supported payment flows, normalized to the Atlas capability model.

Processing
ConfirmationDelayedInstantUPI returns real-time status, although an attempt can temporarily remain pending.
Clearing ModelBatchReal-timePayment routing and account debit happen on the real-time UPI rail.
System Settlement TimingSame dayNPCI settles member positions at scheme clearing cut-offs.
System InteroperabilityOpenPhonePe connects to participating UPI apps, banks and merchant QRs.
Cross-border SupportConditionalUPI International works at enabled QR acceptance points outside India.
Flows
EmbeddedSupportedPhonePe offers a non-redirective iframe checkout.
RedirectSupportedWeb checkout can hand the payer into PhonePe for approval.
Deep LinkSupportedMobile UPI intent opens the PhonePe app directly.
Offline CompletionSupportedIn-store QR and UPI Lite X can complete outside an online checkout.
Manual TransferSupportedUsers can send money to a UPI ID, mobile number or bank account.
Payment RequestSupportedMerchants can send a collect request to the PhonePe app.
QRSupportedPhonePe supports merchant-presented QR for online and in-store payments.
NFCSupportedUPI Tap & Pay and eligible tokenized cards use NFC.
USSDNot supportedPhonePe is app-based; the separate UPI *99# channel is not a PhonePe flow.
Recurring
User-present RepeatSupportedUsers can approve repeat payments directly in PhonePe.
Merchant-initiatedSupportedScheduled debits run after the customer establishes a mandate.
Mandate Support/RequiredSupportedA UPI mandate is required for merchant-initiated recurring debits.
Credential on FileConditionalPhonePe uses the UPI mandate rather than exposing stored bank credentials.
Authentication
Online BankingNot supportedPhonePe UPI authenticates in-app rather than through online banking.
App ApprovalSupportedThe payer reviews and approves applicable payments in PhonePe.
Biometric AuthenticationSupportedEligible UPI payments can use device fingerprint or facial recognition.
PIN / PasscodeSupportedA four- or six-digit UPI PIN is the standard payment credential.
One-time PasswordConditionalOTP is used for onboarding or credential setup, not normal UPI approval.
3D SecureNot supported3DS applies to card checkout, not the PhonePe UPI payment flow.
Authorization
Authorization Hold / Pre-authorizationConditionalUPI mandates and supported block-funds use cases can reserve authority.
Authorization Reversal / VoidConditionalFailed or timed-out debits can reverse; successful payments have no merchant void.
Authorization AdjustmentsNot supportedA completed UPI payment amount is not adjusted like a card authorization.
Partial AuthorizationNot supportedPhonePe UPI does not approve only part of the requested payment amount.
Zero-value VerificationNot supportedPhonePe UPI does not use zero-value merchant payment verification.
Capture
Separate/Manual CaptureNot supportedAuthorization and funds movement are not separated in a standard UPI payment.
Partial CaptureNot supportedThere is no later partial capture after UPI payment approval.
Multiple Partial CapturesNot supportedThe card-style multiple-capture lifecycle does not apply.
Refunds
Full RefundsNativeA merchant can refund the full original payment amount.
Partial RefundsNativeThe refund API accepts an amount below the original payment amount.
Multiple Partial RefundsConditionalUnique refund requests may be used within the remaining refundable amount.
Disputes
ChargebacksSupportedThe payer's bank or NPCI can raise a UPI chargeback with the acquirer.
Non-chargeback Dispute ProcessSupportedUsers can raise a payment complaint in PhonePe and escalate it.
Payment GuaranteeNot guaranteedPhonePe facilitates UPI payments but does not guarantee merchant payment.
Funding Sources
Bank AccountSupportedUPI payments debit a linked Indian bank or eligible NRE/NRO account.
CardSupportedCards are available for eligible PhonePe payments and Tap & Pay.
Stored BalanceSupportedPhonePe Wallet and UPI Lite provide stored-value payment options.
Credit LineSupportedEligible pre-approved bank credit lines can fund merchant payments.
CashNot supportedCash loading into PhonePe Wallet is not allowed.
Consumer Requirements
Local Bank Account RequiredConditionalA linked Indian bank/payment account is usual; UPI Circle allows delegated use.
App / Wallet Account RequiredRequiredThe consumer registers and uses the PhonePe app.
Phone Number RequiredRequiredThe number must be linked to the account; eligible NRIs may use international numbers.
Supported Bank/Issuer RequiredRequiredThe linked bank, card or credit-line issuer must support the selected PhonePe flow.
Merchant Requirements
Local Entity RequiredRequiredDirect PhonePe merchant onboarding requires an eligible Indian business.
Local Bank Account RequiredRequiredMerchant settlements are paid to the registered Indian bank account.
Local Acquiring RequiredRequiredPhonePe and its UPI acquiring partners provide domestic acceptance.
Local Processing RequiredRequiredUPI participant payment data and processing are kept within India.

PSPs

PSP-specific PhonePe implementations, kept separate from the underlying payment method.

Schemes

Schemes connected to PhonePe, using the same four-metric model as the overview.

Scheme
RuPay
UPI

Compliance

Regulators and regulations connected to PhonePe.

Regulator(s)
Reserve Bank of India
Regulation Category

Standards

Standards connected to PhonePe.

Standard Category
PhonePe100%
Markets75.0%PSPs75.0%Schemes100%Compliance100%Standards100%