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
- 351ed91dfd648966942858b837549a11c55d7da27c951ededb408aee3b832b83
- request
- f42890aafbdbae5ad8a7423a5942a7d2decbd78544a079bc157ada81b0f64959
- transaction
- 11e6e97579974eeb40abe36f6ce77f0e29f8fb59347d38e56c874ded9fbe9f0fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28055
the chainentry 28055
- sealed to the entry before
- 89ca1e359e56951c8d24147878012a618702d5bbcdf9e195a198c09250c49487
- this leaf
- 7fb570cc847726fd37fcce1a92f746ea5bc713b94dbd9c33179353e7a7220fe6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cm5HHdhdedF72VMsWll7vvQV1X6jFjIjzNSXEecprExiOa+4KriE4oSH7N0xOYcDb/MIdfGnEsj+/8D3hU+uCA==