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
- 1ab865ffe74f96ccb152051aa2d99a3159d1ffbcdbcef36985851c4419132b5a
- request
- fe02c964daa2f11fd53ef9cb316cfa0bed7e9653f5556d9a57ce5e8d20790903
- transaction
- cc6135d4e5a629ea45aa32a6516f7a9053c7e6526fd877dd893034be23404a6acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20051
the chainentry 20051
- sealed to the entry before
- b36c97b3576874f6a50ce9a9758155fe9aec53a71e64bbfd34acecaf6f89273d
- this leaf
- 4d2f12c5a8a9536a5ed783a59d0c815bf3984e0b4987ce968cb7225ebd4ef724
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- u1CPwwDrkWNqUsKgJ9A6TLnpQbA9ug7uqZ2p+MRP26640anSLh3poeOryekv6KEAir4ckxlNB4ndGL3fso22DQ==