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
- 68af4a25bbafb8d426e6cb88d4cd44c9dd585b09389c8af3e85c42e65f0ff832
- request
- b4cc61232a241816e3f45704b6000d3a7ac8c4e77e1870c0d4249421318e8f63
- transaction
- 5ccf96f9e4d4167764fd11288861914b3e65435022fb04ee838c81930db5b664computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51463
the chainentry 51463
- sealed to the entry before
- c4af83f774dc448ae4994ee98af63953fba992dbffcc5cb304ba5d7109e12e39
- this leaf
- 03947d16127a4a79a9ee071abf28286bb2f83c2768c50d6fb3b074284fcbb10a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oy9yl6U/4srzqYvlzgN0/YQKMEa4MHG2xWZhPe37W8kaqvU0ISzJlvD2YKTH8yE/zV7PN/wTsRyvksBT+cw7AQ==