Buy Now Pay Later software
for digital lenders

HES LoanBox for BNPL is built for organizations that run their own buy now pay later program and want to set the pricing and keep the borrower relationship themselves, rather than pass it to an external BNPL provider. In practice, that covers five groups.

1. BNPL fintechs launching a pay-in-4 or installment product, or moving an existing book to a new platform.
2. Banks and credit unions adding installment options to cards and current accounts, so customers split purchases inside the bank’s own app.
3. Payment providers and acquirers offering white-label BNPL to merchants already on their network.
4. Retailers and marketplaces that want a branded installment plan with their own credit rules.
5. B2B lenders extending pay-later terms to companies rather than shoppers.

Shoppers who want to split a purchase need a consumer BNPL provider.

HES FinTech does not lend to shoppers and is not a BNPL provider. We build the software that banks, fintechs, payment companies, and retailers use to run their own buy now pay later programs under their own brand. You set the credit policy and hold the loan book, along with the customer data and merchant relationships. The platform supplies the engine underneath: checkout widget, decisioning, servicing, and collections.

The difference matters commercially. With a pure-play BNPL network, you rent their balance sheet, their rules, and their take rate. With buy now pay later software, the program is yours end-to-end, and so is the margin. That is why our clients are lenders and platforms launching BNPL, not consumers looking to split a purchase.

Build only if BNPL technology itself is your competitive edge and you can fund a team to maintain it for years. A working stack covers the checkout widget, real-time decisioning, plan servicing, collections, payment rails, and fraud checks, and each part needs updates as scheme rules and regulation change (in the UK, FCA rules for BNPL apply from July 15, 2026). For most lenders, that means several quarters of engineering before the first plan is funded.

If your edge is the credit program, meaning pricing, risk appetite, merchant relationships, and the customer experience, buying is usually faster. You configure products and rules on a platform that already runs in production, and your engineers work on checkout UX and your own risk models.

Some lenders take a middle route. HES LoanBox gives you a configurable core, and if you want full control, the license and source code can be transferred so your team extends the platform in-house. Simpler programs go live from three months; complex ones take longer.

Start with your program model. A direct pay-in-4 product and B2B trade credit sold through merchants need different things, so the model decides what you ask the vendors on your shortlist.

1. Which product and rule changes can your team make without a vendor release? Ask to see a new plan type configured live.
2. How fast does a decision come back inside checkout, and which thin-file data can you connect?
3. What happens to an active plan after a partial refund or a dispute? Check merchant settlement too.
4. Can your scorecard run next to the vendor's model, so you compare first-payment defaults on your own applications?
5. Where are affordability checks and fee caps set for each market, and what records does your compliance team get?
6. What will you pay at your target volume? On small tickets, per-loan fees often outweigh per-seat pricing.
7. If you leave, how do you take your data, and can the source code be transferred?

If most answers point to configuration, you can launch without waiting on the vendor's roadmap. A custom build is still reasonable provided the vendor answers the rest well.

HES LoanBox runs standard BNPL models on no-code settings and adds custom logic on the same platform when needed. Launch takes from three months, depending on scope. Users are unlimited, so pricing does not rise with headcount, and source-code ownership is available as an option.

HES LoanBox runs merchant settlement as a configurable workflow, with payout timing and fee deductions set per merchant and funds moving through the payment providers you connect. You also set the refund rules: once the merchant confirms a full or partial refund, the plan is recalculated on the lower balance or closed, and anything the shopper overpaid goes back through the same provider. On the settlement side, the refunded sum can be netted from the merchant’s next payout. Adjustments stay tied to the original plan and order reference for reconciliation and audit review. How much runs without manual steps depends on your merchant integrations and payment provider.