why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- f0e4778f200648976f2406a0636c7f16ca94a865ab605fe3ad6d03daa0175ac2
- request
- 8f38bb4bfdb5ca943d9c3250b933ce6772d0377a70489dce1281d9ddbb1bdb5c
- transaction
- 67b714d56e758a4c0f94365a6f60562f90ca36604c1a7ab46f030e8fec74264acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39795
the chainentry 39795
- sealed to the entry before
- 24922bf0890efbdc1a1d24ab91066b8f94e19e97d9c7225dd5ef4c246a8ba819
- this leaf
- ad3bcb9913e7cd05177348753a8eb677d868a81ff85593d0ac036bfde6a74b75
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gz9PQda/qoeOEQpWlHBREBHtYqtAJva7/iqVOqpvM1np0wwirwa+rRfMkK+zAr1JSe2DzWHglgzSlgomBBobCA==