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
- 3e3e474f51084f665b3372a5badc014748da9fdaf207b5315e3d1f206a5d4aab
- request
- 572842705ed224e29217c65d97a914034653466d30a919af55c657802cf26222
- transaction
- 324c2ca620466b75f9d7ae5a46b354aff638d0b55759832386c4c7b99bb7d4f9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 96
the chainentry 96
- sealed to the entry before
- ebc59756915757e5c36238a13894ad530c56c83488cccf3139f4c253e2b5f524
- this leaf
- b2f5a9258f4c5bf280884f54033f7b48bba3946b6a85fb9e8241b222b66d5327
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5GsHN2EqJYdIBxKAtmYmKIP2t/yjcgwahhEKq74g53sKp8FNsqWBklx65gQr4n0OkaFZmjAnBmBnVwxlLlIVDA==