Payment integration
PhonePe payment paths in Invoice Crowd are currently retired while the integration awaits current Standard Checkout v2 credentials and verification.
Last updated:
Configuration to settlement
Connection, customer checkout and final settlement are separate stages. Read the status and limitations before showing the method on a live invoice.
Credentials and mode stay tied to the selected business.
Do not configure PhonePe for live collection until Invoice Crowd publishes a current supported credential and checkout contract.
PhonePe and merchant availability are provider-controlled; Invoice Crowd must still complete the current v2 integration contract.
Availability is evaluated before a customer enters checkout.
No PhonePe invoice checkout is currently enabled. Saved legacy credentials are retained for compatibility, not advertised as an active payment method.
No PhonePe subscription path is enabled.
The final local state follows provider evidence, not the browser.
The retired routes return a fail-closed unavailable response and cannot mutate invoice payment state.
This is an availability notice, not an active integration page. Use another configured gateway for current collection.
Integration facts
The fields below describe the current Invoice Crowd path; the provider remains the source for merchant eligibility, fees and regional availability.
Not currently available
No PhonePe invoice checkout is currently enabled. Saved legacy credentials are retained for compatibility, not advertised as an active payment method.
No PhonePe subscription path is enabled.
Do not configure PhonePe for live collection until Invoice Crowd publishes a current supported credential and checkout contract.
The retired routes return a fail-closed unavailable response and cannot mutate invoice payment state.
PhonePe and merchant availability are provider-controlled; Invoice Crowd must still complete the current v2 integration contract.
This is an availability notice, not an active integration page. Use another configured gateway for current collection.
Amount, currency and allocation are derived from the current server-side invoice state.
A provider screen or browser return is a locator, not sufficient settlement proof.
Durable attempts and stable provider identities prevent an uncertain response from becoming an unbounded duplicate payment.
Gateway fees, exchange costs and settlement timing come from the merchant agreement, not the Invoice Crowd subscription.
Configure another active provider when this gateway does not support the merchant, customer, currency or collection model.
Questions
Current status: Not currently available. No PhonePe invoice checkout is currently enabled. Saved legacy credentials are retained for compatibility, not advertised as an active payment method.
Do not configure PhonePe for live collection until Invoice Crowd publishes a current supported credential and checkout contract. PhonePe and merchant availability are provider-controlled; Invoice Crowd must still complete the current v2 integration contract.
No PhonePe invoice checkout is currently enabled. Saved legacy credentials are retained for compatibility, not advertised as an active payment method.
No PhonePe subscription path is enabled.
The retired routes return a fail-closed unavailable response and cannot mutate invoice payment state. A browser return or posted status alone cannot settle the invoice.
No. Provider transaction fees, foreign-exchange costs, settlement timing and account terms are controlled by the gateway and merchant agreement. Check the provider before activation.
Browse the current integration directory and choose a gateway that supports the merchant, customer, currency and collection method today.
