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
- 0bb91a8a4467d3472f9264bdeba9a932b3c7d931ff20bafdb4b472b95b0cbb39
- request
- 9938717887ae8310f3155eeb0fbc68ea2d43ca12716d69505840a4f7395ca9f0
- transaction
- 2da4d7d7cb69bd547c3d5775040289c75719d0de8570b239db5d2eb927816555computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62455
the chainentry 62455
- sealed to the entry before
- 15f9dcceecd0a98b441991ebd8eb0eb41b2c279873f53c19d078677731e06654
- this leaf
- 102d3ceef84a9353be7c2650c60e607d0f957bd4d02044779483c3298741701e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Pn2IYA0bqbT78i5R+rNrClV0x3a+Kee5ApjviDwfadNl7WDCZY9jqY/fbLjQbvtr6Je+oyX/oLY6gf5BYexyCg==