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
- 61b425e8e64ee4975fa42561e0ef75cd9d8cea9882792021f39bc05eb613633a
- request
- 02ee2ab8bacf076a6219918c6c25d992987b408dbf2b8806d1a3c7642dafe069
- transaction
- d136806b832ad5afa621c991c2200191cfc744d2c6450887b3b3d9782f88c369computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42756
the chainentry 42756
- sealed to the entry before
- bed85190657164d3c8f278ac3014474127e2426b3478bf07a60e9782fd688ace
- this leaf
- d095e6a5aae27f6bc7af452a2507fd22cf771cbc2dc1a67924b87c0cfa65f379
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pZq0ICKmykrRf6jP2ygaGDYHGUAKX4h92ewhB/JQRDjFLoeZDWNDsxLFYO6Us1q7bhjvZmeHKiMNrRfm1i+UBA==