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
- e0ed5c103ff441bd76170849baf67419cc19f60d1e4b38263de30e25fd0d7268
- request
- ae99d3b80ae9b23fac01258321c7c4efdcd2bdaf46ebe01f0b629aa65b671f6b
- transaction
- 71a6b9cce28ad90f7409713034bdcb32299a1ffb2c28890ef47170c46ceab877computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76372
the chainentry 76372
- sealed to the entry before
- c943812ae43a0e68485a4b9f843207d30b27d39fc8cda10a59351cf2600a4dbc
- this leaf
- 6e0d5791cf68ecb8a43a2153275c4d8895e123205bf7165a4a0b3a7af97c1fc8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8JS5CDF5+l93XcPHmQHZx/dwaGXn6hRMbnvu+BY6ww2wdH+12sqdPKID9+jPt13YdezXJ9aFRB4vj3Grwb44Cw==