Checkout credit eligibility stays on the lender’s side

Every eligibility change is a partner integration ticket. Decisimo runs the lender's policy in one call.

Start free See the decision stages

Checkout credit policy stays on the lender’s side

Lender-side eligibility

The partner calls one endpoint to run the lender’s policy

Merchant and market rules

The risk team edits rows, each with an offer reason

Rule changes

The partner keeps its URL after the risk team releases a change

Shared policy

Market and merchant conditions select offers in one table

Market additions

The risk team adds rows and releases them

Source failure handling

Absent values carry an error flag, and catch-all rows set what follows

A checkout, from partner call to offer

  1. Checkout request

  2. External data

  3. Merchant and market rules

  4. Affordability score

  5. Financing options

  6. Test a rule change

  7. Release to endpoint

Merchants and markets as rows the risk team edits

  • Conditions and resultsMarket, merchant category and affordability set the offer and its reason
  • New marketsAdd rows, each with a plain reason beside its offer
  • Row orderLast match wins by default, or set first match to win
Financing options decision table maps market, merchant category and affordability conditions to offers and reasons
Financing options assigns instalments, pay in 3 or invoice after delivery across seven market rows.

Three lookups together, and what happens when one fails

  • Three sourcesThe three calls overlap, and the slowest source sets the wait
  • Source errorsAbsent values carry an error flag. Catch-all rows set what follows.
  • Cached lookupsA maximum age lets the lender’s database serve a repeated lookup
Data source dialog for “Eligibility lookups” listing Credit bureau, Device and fraud signals, and Merchant profile
Eligibility lookups groups Credit bureau, Device and fraud signals, and Merchant profile in one data source.

Test a change on chosen values before release

  • Test runRun the whole decision flow with external calls switched off
  • Run recordSee each stage’s output, ending with the offer and its reason
  • Release recordEach result is tied to the release that produced it
Testing studio single run showing input values and the resulting offer, reason and release
Checkout eligibility runs six steps, ending with six instalments and “UK, affordability clear”.

The partner keeps the same endpoint

  • New releaseA changed rule runs from a new release on the same endpoint
  • Sign-offAn endpoint can require sign-off before a release is deployed
  • Revision historyEvery save is a revision, and two releases can be compared

Endpoint and release practice

The lender keeps the legal duties

  • High-risk creditEU AI Act duties start 2 December 2027. Article 22 applies today.
  • Lender’s dutiesPartner distribution does not transfer either law to the partner
  • Decision recordsInputs and outputs can go to the lender’s Postgres for portal review

AI Act and Article 22

What stays with the lender

  • Demo valuesEvery threshold, score, market and offer shown belongs to a demo case
  • Lender’s policyThe lender writes the policy and supplies the data. Decisimo runs it.
  • Partner surfaceThe partner owns the checkout and any screen it provides

Questions we get asked

What is a BNPL decision engine?

A BNPL decision engine applies a lender's credit policy to checkout information and returns a financing offer. Decisimo runs merchant and market rules, an affordability scorecard and a financing options table in one decision flow.

Can I add a market without a partner release?

Add rows for the market in the financing options table, then deploy a new release to the same endpoint. The partner keeps calling the same URL.

How do fraud checks fit into checkout credit decisions?

Decisimo can call device and fraud data with the credit bureau and merchant profile, then apply the lender’s rules to returned values. See fraud decisioning

Set checkout eligibility on your terms

Start free