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
- f81807cfff0cb8ab79745744bffcaf9beb4ca9f19647e35f9bfb6ab70a55dc1f
- request
- cdf2f65a10aed74512d1c2017642dc07f0134bafcaf0472a666396df93606ab0
- transaction
- 362609629c79e314252684a4924385a1940bdd33f9e920d561fda5a8dff11dbacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23018
the chainentry 23018
- sealed to the entry before
- bccead9e260bfb3ebb6388e3819828fa910c16d7498f99ce43e40e0b164affcb
- this leaf
- 042647b501de3efda210faa8f7ba3d7f0a272fe0d1b3ee2dd96a9c1b2c040d08
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RfFDO6H8KdcnUoLDptmUakqGDyeahtO/pcsxswQXv2yHStjOwe9IK6/h5njGEQ7f2neuq9BYfsFR4kb4xgWUDw==