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
- 5fb010ee8e5549ac3c39e54c0659962b8bc36912d43a0bc2fac8daf4c833dfdd
- request
- 0b84f51745c43c94522b00d8dc9f813c31ed13c66b24fb88331eaf3ece9a70bf
- transaction
- 438e2805ddc221e8aa2d640ebe8b19c6b703e32f0191add060e0c6a029820120computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21667
the chainentry 21667
- sealed to the entry before
- 32e4511456efea33d548d0dce95e3f18b50e73903b2ac118e6f28a2911ae96c2
- this leaf
- 0f27892554000207fa7e6380b4ebd2bda3c7375b21d6844a6a8ae81dcf01dfbe
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Gs1I+e5nDpo3hEYA90X3RiB4fctcboxewLEmciLop5x8ZrVJREYFqUGBIbd6lG7mh2NmTW/SwyxyPHhE5iQyAg==