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
- 15b663efb0d17487108826440f9c53999410a2b66ea38554fe356a8b0bf77062
- request
- 4699e310e49ef3f3fcb93cc7bdf88e350a8c2615168518fbadc27177ef374120
- transaction
- 2835b0a806b2f772f5d02fc0f24dccd5e9fc881cca59c4571bd71d9844db7bcfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14702
the chainentry 14702
- sealed to the entry before
- c267cf46a0bbe30ea4f9512892962b0b228dba879d26df6f69bad1cdc6299184
- this leaf
- decafb59331611a2a5d0fa2c01edc2a3615268e221ea43d4b828ea4a802de0d3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3txDYCEbFCAKrv+QKsBaeKwHGL+nkv8Td/HADUACjZQCgyA5t2OILnz0HO/tCKNXVJviA97v8VVBjAH/i7ACBw==