On 17 August, Bank Indonesia launched Kartu Kredit Indonesia (KKI), a domestic credit card scheme funding QRIS payments by scan or tap. Eight major banks issued at launch, including BCA, Mandiri, BNI, BRI, CIMB Niaga, Permata, Bank Mega, and BSI. Online payment gateways and physical cards will follow, with the Indonesian Payment Systems Association expecting roughly 10% of existing credit card volume to transition to the new scheme. 

Institutions outside the initial eight launch banks can now use the new rail to build and deploy distinct credit products. 

This is your chance to get in at the beginning of a major exciting new development happening in Indonesia… 

If your core doesn’t hold you back.  

Capturing credit card volume on Indonesia’s new QRIS rail 

Consumer credit demand across the region is surging. In the Philippines, consumer loans covering credit cards, car finance and salary advances grew 19.6% year on year, card payments are forecast to almost double between 2024 and 2029, and BNPL users are overwhelmingly millennials and Gen Z, at more than 75%.  

Credit products are where the growth is across the region.  

But while connecting to a national rail gives you baseline access, product design will be what truly determines market share. This is because every institution will eventually leverage this shared rail, so connecting to the rail itself will not be your competitive edge. Credit limits, pricing, the fees, who it’s designed for and how it behaves in the customer’s hands will be your defining edge.  

Get there first  

New rails, changing customer behaviour and new regulation create credit opportunities faster than traditional bank development cycles can respond. New categories reward whoever shows up early with something credible. The first virtual credit products on the new rail will set customer expectations while the category is still forming, and catching up later costs more than arriving early. That’s most pressing for institutions outside the launch group, who start the race a step behind the eight banks already issuing. 

Which brings you to the practical question: how long would it take your institution to launch a virtual credit product today? If the answer is less than a few months, you’re missing a key opportunity. 

What launching a credit product takes 

A credit line or card is a demanding product to run. It is a revolving relationship with a lifecycle of its own: 

• A credit line with a limit that can move, up when the customer earns it, down when the risk changes 

• Utilisation tracked in real time, because every authorisation depends on knowing what’s left 

• Interest accruing on a balance that changes daily 

• Fees that differ by segment, by channel and by behaviour 

• Drawdowns and repayments, with allocation rules and statements, minimum due and what happens when a payment is late 

• Exposure, tracked across the product and the portfolio 

Legacy core systems were engineered for fixed instalment loans, which feature static amounts, predictable schedules, and simple ledger entries. They struggle when forced to handle revolving credit lines, dynamic limits, daily interest calculations, and complex repayment waterfalls, which means any launch product involves the tech team working so much slower than your product team. 

There is an answer to this.  

There is a way to launch credit lines in Indonesia (and beyond) in weeks without touching your core.  

We’d like to introduce you to: Oradian's product engine.  

With a product engine, your credit products run on the product engine alongside your core, as configuration your team controls: credit lines, limits, utilisation, interest, fees and repayments, and the whole lifecycle.  

So your core keeps run-the-bank operations as they are, while you’re able to launch as many credit products as you can within your current team, with total control over your infrastructure.  

Real-time or nothing 

With credit products, authorisation happens while the customer stands at the till or sits in the checkout, so the decision, is there limit available, does this pass the risk checks, has to come back instantly. Sub-100ms API response times, like those offered by Oradian’s product engine, are what make that possible at volume. And an AI risk signal can tighten a limit today instead of at the next review and reward a good customer the same way. 

How work is divided across teams with Oradian’s product engine  

A dedicated product engine establishes a clean division of labour across your company: 

• Product and risk teams: Manage commercial parameters directly, setting credit limits, interest matrices, fee structures, eligibility criteria, and billing rules through built-in approval workflows without submitting vendor tickets or waiting on IT releases. 

• Engineering teams: These teams focus on integration architecture. Developers connect the product engine to peripheral systems, including card processors, payment rails, scoring models, and mobile banking apps, all using Oradian’s 750+ versioned REST APIs. 

• Development teams: Dev teams can use Custom Code when unique product rules are required, fully governed within the platform and accelerated by embedded AI authoring tools. 

What gets better and how you’d measure it 

Here are some of the areas you can expect improvements in credit line product launches when using a product engine:  

• Time from decision to launch comes down to just weeks 

• Cost per product change, falling because changes can be made through configuration without the need for vendor change requests 

• Approval turnaround on limit changes can happen on the same day 

• Credit product launches are set by your roadmap instead of your vendor’s 

Get control back  

A credit product that can change quickly raises an obvious question in a risk committee: who’s controlling the changes? Every change is approved, versioned and reversible, with a record of who did what and when. Your general ledger stays the single source of financial truth, and every accrual, fee and repayment posts to it in real time. The audit trail gets better, and so does the speed. You don’t trade one for the other. 

Oradian: your key to launching credit lines quickly   

Launching a virtual card or revolving credit line on new national infrastructure usually hits a wall because legacy cores cannot support daily balance recalculations, real-time limit updates, or changing fees. Upgrading those legacy systems is slow, expensive, and unnecessary. 

Oradian sits alongside your existing core as a specialised credit product engine and integration layer, taking over the complete operational lifecycle of revolving credit. We provide the credit product engine and the open integration layer that sit behind a virtual card proposition, running the credit line, the limits, the interest, the fees and the repayments, and connecting to the local payment and processing ecosystem through APIs. 

Here are some of the ways Oradian can enable you to scale and build credit lines:  

• Credit line management: Configures flexible limits, tracks real-time usage at authorisation, and automates limit adjustments based on borrower repayment behaviour or incoming risk signals. 

• Interest and fee calculations: Handles daily variable interest accruals, late payment fees, channel-specific charges, and tiered pricing structures without requiring custom core scripts. 

• Repayments: Manage allocation rules across principal, interest, and fees, while managing billing cycles, minimum amounts due, and statement generation. 

• Ecosystem connectivity: With Oradian, you can connect directly to local card processors, national payment switches, credit bureaus, AI scoring models, and mobile banking applications through 750+ open, versioned APIs. 

How fast could you launch? 

The new national rail removes technical friction on the payment side. What remains is an execution race: how fast your teams can design, configure, and ship revolving credit products to market. 

If virtual cards or credit lines are on your roadmap, talk to our team at vanda.jirasek@oradian.com to set up a product engine demo.