Eligibility comes first
The bank sanctions a line and defines limits, pricing, repayment terms, and eligible use.
Put sanctioned credit to work at the point of purchase. Explore the customer journey, issuer economics and a bank-app EMI proposition enabled by PhiAMS.
Illustrative proposition. Eligibility, app enablement and actual outcomes depend on the issuer programme.
Select a stage and switch perspectives to see what each party experiences.
The bank sanctions a line and defines limits, pricing, repayment terms, and eligible use.
The customer links the line and selects it as the funding source before confirming a payment.
Statements, dues, interest or fees, and collections follow the bank’s credit product terms.
The customer buys time to repay. The merchant weighs acceptance costs against additional sales. The bank earns income while funding the balance and carrying credit risk. Explore each side below.
A single purchase, repaid in full at the end of the selected period. No interim repayments or compounding.
Interest = purchase × annual rate × days ÷ 365. A grace-period example assumes all conditions are met and repayment is on time. It is not available on every line.
Processing, renewal, EMI, late-payment, and foreclosure charges can change the cost materially. Check the issuer’s disclosures and repayment terms. Rewards do not reduce the amount due unless actually credited against it.
Set your merchant discount rate (MDR), margin, and the share of credit-funded sales that would otherwise have been lost.
MDR is the merchant’s acceptance fee. Interchange is an issuer-side component of payment economics, not an extra fee added on top of MDR in this example. The baseline rate is a comparison assumption, not a claim that all other UPI payments are free.
Sales uplift is a hypothesis to measure, not a guaranteed benefit. Merchant refunds, disputes, fraud obligations, device or subscription costs, and settlement terms still depend on the acquiring agreement. The contribution example excludes those additional overheads.
Compare Credit Line Interest Bearing (CLIB) with Credit Line Interest Free (CLIF). The profit bridge is an annualised run rate at the selected portfolio age, per active account and for the whole portfolio.
Scenario values are illustrative, not a bank quote or NPCI tariff.
| Line item & calculation basis | ₹ / active account | Portfolio · ₹ lakh |
|---|
Isolated annual effects per active account, with every other assumption held constant. 1 percentage point = 100 basis points.
Match these definitions to the labels in Editable assumptions. All percentage inputs use percentage units: enter 0.60 for 0.60%, not 0.006. Rupee inputs exclude GST unless explicitly stated. Examples below are fixed illustrations; the profit bridge reflects your current inputs.
A proposed journey for a bank that issues Credit Line on UPI and also offers its own UPI payment app. The app presents eligible plans during merchant checkout; the issuer books and services the resulting instalment loan through the approved bank and PhiAMS design.
Approve the eligible cohort, transaction thresholds and merchant categories; set tenures, rates, fees, offer validity, limit use, refund and foreclosure rules. Decide whether the EMI is issuer-funded or includes a merchant-funded offer.
Have the bank's UPI app and payer PSP retrieve eligibility and offers, display terms, capture selection and UPI PIN consent, and show confirmation or a clear decline. App support is separate from line-linking support.
Integrate PhiAMS, bank BRE, lending ledger/CBS and GL for real-time checks, exposure, EMI booking, schedule, interest and fee accounting, billing, collections, closure and reporting.
Through the bank, confirm NPCI's current Credit Line on UPI Issuer and Credit Line on UPI–EMI Issuer scope, plus the payer app/PSP scope and any acquirer-side requirement. Complete the assigned scripts and production enablement.
Verify a valid merchant QR, permitted category and acquiring acceptance. Merchant or aggregator collaboration is needed for a merchant-funded, brand-funded or item-specific offer; it is not assumed for an ordinary issuer-funded plan.
Approve disclosures and consent evidence, real-time reconciliation, duplicate and timeout handling, full/partial refunds, disputes, repayment method, servicing scripts and a limited pilot with measurable exit criteria.
Illustrative iPhone-style bank app and secure UPI PIN sequence · electronics purchase ₹12,000 at Croma.
* Hypothetical 6-month plan at 24% p.a. reducing and ₹0 fee; rounding is illustrative. Actual APR, fees, due dates and disclosures depend on the issuer. Croma is used solely as a familiar retail example; no affiliation or live integration is implied. The secure PIN screen is schematic, not a reproduction of NPCI’s Common Library.
Illustrative merchant acquiring portal · ordinary issuer-funded EMI purchase.
Item: eligible purchase
The customer chooses the funding source in their app.
Original UPI reference linked to refund instruction.
A merchant-funded or item-level promotion would require additional commercial and integration arrangements.
Illustrative issuer operations view · PhiAMS and bank-system responsibilities are configured per deployment.
24% p.a. reducing · ₹0 processing fee
Screens depict a proposed operating pattern, not a live PhiAMS interface or an NPCI-mandated message sequence.
Customers with an active eligible bank credit line may see it for qualifying merchant purchases. The bank decides eligibility using the amount, available limit, merchant category and its credit policy. The option will not appear for every QR.
In the supported bank UPI app, after checking the merchant and amount and before entering your credit-line UPI PIN. Review the terms displayed for your own transaction before accepting.
Where the bank offers both choices, you can choose the standard credit-line payment instead of EMI. The app should clearly show which option you are authorising; available alternatives depend on the bank's product.
No. The merchant receives the completed UPI payment according to its acquiring settlement arrangement. You repay the bank in instalments according to the EMI schedule.
Check the bank's offer for the interest rate or APR, processing fee, applicable taxes, monthly instalment, total repayment and any late or foreclosure charges. These vary by issuer, customer and offer.
Yes, the purchase uses the sanctioned credit line. How your available limit is restored as instalments are repaid follows the bank's terms, which should be visible in the app or statement.
The merchant must initiate the refund. The bank then adjusts or closes the linked EMI under its disclosed refund and foreclosure policy. Check that policy before confirming; fees and interest already charged may require separate treatment.
Keep the transaction reference and contact the issuing bank through its official support channel. The bank must investigate payment, reversal and loan-booking status together; do not assume a failed payment has automatically cancelled the loan.
Only if your issuer and app explicitly support post-purchase conversion. Availability at the time of purchase does not mean a later conversion is available.
Use the repayment methods and due dates stated by your bank. AutoPay, if offered, needs its own mandate authorisation. Ask the bank for its foreclosure amount and applicable charges before closing early.
Public references: HDFC Bank's documented on-scan EMI journey · NPCI certification onboarding · RBI pre-sanctioned credit-line framework · NPCI confirmation before Common Library PIN · NPCI Common Library role.
PhiAMS connects bank-sanctioned lines to the UPI journey. Issuer systems update pre-sanctioned lines in PhiAMS; its origination module handles discoverability, consent and confirmation checks before activation. The bank retains lending policy, funding and credit risk.
Reference architecture. These diagrams explain a proposed bank integration pattern, not a production deployment or implementation specification. Detailed service boundaries, API contracts, system-of-record ownership, security design and deployment choices are agreed during solution design. Arrows show messages and integration, not movement of funds.
Sanction and policy, pre-sanctioned line updates, BRE decision rules, customer terms, capital and funding, regulatory obligations, credit losses, and oversight of outsourced operations.
Configure the programme; respond to line discovery; record consent; invoke BRE verification at confirmation; activate the approved line; manage accounts, limits, payments and billing.
The NPCI switch connects directly to PhiAMS. Bank-approved BRE, core banking, KYC and bureau services, risk feeds and communication providers integrate as scoped.
Select a component to inspect its proposed inputs, processing, outputs and exception controls. BRE = business rules engine; GL = general ledger. This is a detailed logical view; physical topology, database choices, endpoints, performance limits and recovery targets require a bank-specific low-level design.
These are proposed interface and control steps; the bank-specific contract defines message fields, consent evidence, retry rules and timeouts.
These are recommended acceptance criteria for solution design and testing, not a claim about a bank’s current production configuration.
PhiAMS capabilities and the banking outcomes they are designed to support. Delivery scope and configurations are agreed with each issuer.
Connect issuer systems and the NPCI switch through defined interfaces.
Bank value: clearer integration boundaries.Event-driven microservices separate technology layers and lifecycle functions.
Bank value: scope changes by capability.Shape limits, credit controls and repayment structures for customer segments.
Bank value: differentiated programmes.Handle discoverability, consent, BRE verification and activation alongside authorisation, billing and servicing.
Bank value: fewer operating hand-offs.Maker/checker, audit logs, risk controls and data-localisation features.
Bank value: traceable programme operations.Understand credit usage, repayment patterns and customer behaviour.
Bank value: informed portfolio reviews.| Workstream | Bank contribution | PhiAMS / joint delivery | Exit evidence |
|---|---|---|---|
| Product & risk | Approve segment, pricing, underwriting and disclosures. | Map policies to product parameters and credit workflows. | Signed product rules and representative test cases. |
| Integration & data | Identify source systems, owners, interface access and GL mapping. | Agree APIs, message mappings, ledger ownership and exception handling. | End-to-end traces and reconciled financial postings. |
| Security & readiness | Set control requirements, operating ownership and approvals. | Validate access, audit, performance, recovery and applicable network tests. | Accepted test results and required certification/approvals. |
| Pilot & operations | Approve pilot cohort, service procedures and exposure limits. | Monitor decisions, reversals, dues, reconciliation and collection hand-offs. | Pilot sign-off against agreed operating and risk measures. |