Skip to content

chore(POCP-1226): support 8-digit IINs in card event - #279

Draft
lukasz-k-bieszczad-cko wants to merge 10 commits into
masterfrom
chore/POCP-1226/allow-8-digin-inns-v2
Draft

chore(POCP-1226): support 8-digit IINs in card event#279
lukasz-k-bieszczad-cko wants to merge 10 commits into
masterfrom
chore/POCP-1226/allow-8-digin-inns-v2

Conversation

@lukasz-k-bieszczad-cko

Copy link
Copy Markdown
Contributor

Alternative to #270

Card.getIIN emitted a flat 8-digit IIN for every scheme, over-exposing
the BIN for schemes the backend caps at 6 (notably Amex). Mirror the
allow-list in api (controllers/card_inn.go): only visa, mastercard,
discover, jcb, union-pay and carte bancaire surface 8 digits; every
other scheme - plus unknown or co-badged/ambiguous prefixes - falls
back to 6.

Applies to both consumers of getIIN: the emitted card_iin field event
and the Dynamic Checkout restrict_to_iins prefix match.

Note: the backend api-deactivate-eight-digit-bin LaunchDarkly flag is
per-project and server-side, so the client cap is scheme-based only.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant