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
- 84de6d788da1eb9964a14389c7dcdb1d2f3e704eb7582cf9510a8433e173094d
- request
- 3c8d9be17baf3d63675db0ebe6c850df31cfbf737fb199a6266b851fc15d707a
- transaction
- 12fb813cd13acc7d196758bc5d01b2c89344b59f60c391ad252074b9fc4d05decomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55878
the chainentry 55878
- sealed to the entry before
- e6dcf8a66d3092eca83424cb8a9cfe0d7c7131b25aabea1757f6c11c64a359f3
- this leaf
- 4f56e9f063504dda687ff6851ad6bd612edab539a3bcb6a871ff02552ff17b0b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ohujSZWnuoSpOLg53u6aGp0rgkJG5fE19tSj/pN0AvCABSSSUofOcS5bga02rBJrWDRT1P1P11u1+sHbQIPkAg==