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
- 438eee2fbff6f7332f9b51d33c9531b535028b28f1dcca27a2026511f75a2985
- request
- 71f0a966e9739c233b7e7c98f80b69f88ab76f5f83c5c1a164b2343a7f2cec26
- transaction
- c0020124cdb383778722b9e262004d76aa3812c9e09eaa49baeaa0c9defe8e7fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60044
the chainentry 60044
- sealed to the entry before
- 0275d92eb23d0ebfdb90c8f31f9561a3ce2646c51776811b1bd6f5c9743fb526
- this leaf
- 0634c0fc6bbecfad8410c230f436d80fa12aa1032c36fd56a7abaf678ab5d4f6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- S4peeqGI++74JvqqyrEVWI8F5fvEJko47z3Q4ZuSrXI/LVFZyoeMK56hY2ejnbsek3NEJy1NRnQAwNoyhZVTDQ==