PAYMENT INFORMATION · Workflow idea
For an approved information lookup, use only the permitted card-number prefix to retrieve general details such as network, card type, issuing bank, and country. Never collect or store a full payment card number for this purpose, protect lookup records, explain that issuer data can be incomplete or outdated, and do not treat a prefix result as proof that a payment or cardholder is legitimate.
01 / The starting point
A permitted prefix and a limited information-check purpose
“Show general issuer information while keeping payment credentials and fraud decisions protected.”
02 / The work
Helps an authorized user retrieve general information associated with a card-number prefix.
Accept only the minimum prefix needed and reject full card numbers or security codes.
Show the network, card type, issuer, and country only when the source returns them.
Flag missing or uncertain details rather than filling gaps by guess.
Avoid retaining payment data and limit access to any necessary lookup record.
Do not approve, decline, or label a transaction based on issuer information alone.
03 / The result
A qualified lookup result with source timing and no full card data retained.
Reviews & approvals · Example outcome
A qualified lookup result with source timing and no full card data retained.
A prefix lookup does not verify a cardholder, account balance, or transaction. Never request a full card number or security code, treat results as informational, and use approved payment controls for any transaction decision.
04 / Make it yours
A few choices shape the work around your team.
Accept only permitted prefixes and avoid storing payment credentials.
Document the source’s coverage, freshness, and limitations.
Mark missing or approximate issuer details as unverified.
Use the organization’s authorized payment process for transaction and fraud decisions.