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
- eddb7503f40ab70b4dc6993fd5f1dc1c96bf3ecab9713c3e52bf50ec8d715542
- request
- ab4da744f49474b5e90aac897cfc433f736a3f6365025af53ec9475d1c26833f
- transaction
- 9d702118915b28f805e52b9547612a02ee627727819b747cf17b51939ef63e73computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37314
the chainentry 37314
- sealed to the entry before
- 9b4fd6009b6a586f8a06661d2efebab0a9176573d9f35e509805e6af3b464928
- this leaf
- 2805433aebd93613a75ada2f2b73d6897524bdf5f0948143c1d913978c4c8533
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iBKJUrLB5+z71cVFETIH8MAH5VnxzXvEg72tPgDk2n3sfAnPD5wM/DzSriF+ixcjCalBrPdwvyXlHytHOqTpDQ==