Paymentology: Lume issuer processing, fraud decisions and programme responsibilities

The issuer processor receives authorisation and operational messages and can enforce configured risk and programme rules, but the issuer remains the party responsible for its regulated banking relationship and cardholder obligations. This means card transaction speed, availability and jurisdiction restrictions must be scoped to a specific programme rather than inferred from the supplier’s global footprint.[3][1]

The BIN sponsorship service matches customers with a licensed institution whose BINs fit their markets and card programme. The customer establishes a sponsorship agreement, and Paymentology integrates the sponsor’s systems with its processing platform. Sponsorship enables a defined programme; the issuer’s eligibility and contractual requirements still apply.[11]

In production, the most important interface is often the authoritative issuer ledger, not the branding on the payment card. Authorisation holds, reversals, clearing amounts, FX adjustments and chargebacks should reconcile to the financial account from which funds are drawn. Each party needs a written definition of who can suspend a card, release a hold or adjust a completed charge.[3][4]

Lume’s published infrastructure uses multiple cloud providers and an active-active design. The product page describes regional deployment choices, redundant servers, tokenisation and identity-based access. The programme’s agreed hosting topology, recovery tests and issuer/network fallbacks determine its actual service continuity.[6][2]

A proper comparison distinguishes processor charges from the regulated issuer/BIN sponsor, scheme assessment, card production, fraud and chargeback cost. A low fee for authorisation processing can coexist with a substantial programme minimum, FX spread or annual audit commitment. The public service descriptions do not provide a reliable blended fee for all clients.[1][3]

Decisions about debit, prepaid, revolving credit, crypto-linked cards and BNPL can materially change the compliance and financial model. The Lume announcement discusses several products, but commercial availability and term sheets should be confirmed for the precise licensed issuer and geographic programme.[2][9]

The delivery plan should begin with issuer and BIN-sponsor eligibility and a list of countries, card products and network schemes. Follow with ledger authorisation, KYC, sanctions and fraud policy, transaction limits, chargeback operations, scheme messages and customer account reconciliation. Front-end app readiness is not proof that the payment network will accept the programme.[3][7]

The public contact page directs Lume technical enquiries to an authenticated customer-support centre. The developer guide links card and transaction lifecycle documentation, FAST messages, remote messages, scheduled reports and the card-test simulator. Contracted support sets response times and escalation across the processor, issuer and programme manager.[9][13]

For global card programmes, support needs to reflect the scheme’s local calendar and time zone, not only the location of the processor’s central office. Contracts should identify responsibility for declines, chargeback disputes, lost or stolen cards and security incident notifications.[10][5]

Paymentology supplies technology supporting regulated issuers. The bank or other authorised issuer, not the software processor by implication, is responsible for the deposit product, BIN sponsorship and regulated account terms. Network and scheme eligibility are additional commercial and operational requirements.[1][3]

PCI and 3D Secure implementation help payment security but cannot be presented as prudential regulatory permission or as guarantees that all cardholder losses are reimbursable. Each programme needs its own entity and country-specific disclosure of protections, fees and card use limits.[5][2]

Paymentology is an issuer-processing group with a London head-office presence and global delivery. The group describes a 2021 combination of Tutuka and Paymentology, and its subsequent platform development culminated in the June 2026 Lume launch.[8][2][10]

The Banking.Live 3.0 notes published on 19 August 2026 deprecate the legacy personalisation-data endpoint and specify migration to a PaySecure replacement once released. Integrators should confirm replacement availability for their deployment before cutover. The same notes restore visibility of non-triggered decision rules and change dispute re-presentment handling for internal-ledger clients so the event is logged without deducting the balance.[12]

Operator

Paymentology group and specific issuer-processing operating/contracting entities

Service scope

Technology provider for issuing, processing, authorising and servicing payment cards, with real-time transaction controls and issuer programme interfaces; the technology vendor does not automatically serve as the BIN sponsor, licensed card issuer or deposit bank.

Customer types

Licensed banks and card issuers; Fintech and neobanks; Remittance and broker-wallet businesses; Programme managers; Lenders and embedded finance platforms

Delivery

API; Hosted; SaaS; Managed service

Pricing publication

Quote only

Headquarters

London, United Kingdom

Platforms

Lume; Decision Engine; Fraud Control Services; Client Portal; Developer Portal

Integrations

Issuer core ledger; Card networks; Bank sponsor; 3D Secure; Decision Engine; Webhooks

Pricing scope

No universal published per-card, per-authorisation or annual platform fee. Quote must identify setup, sponsor and BIN fees, transaction processing, fraud/3DS, tokens, FX, chargeback management, reporting and support by region.

Implementation

A card programme requires issuer/BIN sponsorship, network approval and programme compliance alongside the processing API, available currencies, risk decision rules, reconciliation, tokenisation and incident control. The June 2026 Lume launch expands the product stack; a future feature in marketing is not a confirmed live client entitlement.

Support

Commercial enquiries, a developer portal and an authenticated customer-support centre. Programme-specific contracts allocate operational support, cardholder disputes, network outages and response commitments.

Permissions and regulatory scope

Card issuer processor/technology role must be separated from the authorisation of the sponsoring bank or licensed issuer, the card network and the individual programme manager. PCI and technical-security claims do not create prudential or client-money permissions for every partner.

Provider metadata checked 22 Oct 2026Source 1Source 2Source 3Source 4Source 5Source 6Source 7Source 8Source 9Source 10Source 11Source 12Source 13

For procurement, ask for the exact issuing bank and BIN arrangement, network list, supported currencies and cards, customer funds flow, issuer ledger reconciliation, dispute responsibility, transaction rules, fraud-policy ownership, tested failover, implementation plan and line-item charges. That mapping determines whether the platform is fit for a particular brokerage product.[3][5][7]