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
- 296ae5d67b5bd1d2fcacf84d2bf98315640671f32a8917822e7b5d650795a463
- request
- b3a7d40da78c362694333cf3fe0c4e618b9f2e9da785b6d1aade55b430da7da7
- transaction
- 1630f3a1dbe1784e53b0a278b6b31bcaa49aed29ab193ebf3dd05739a49220e3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43771
the chainentry 43771
- sealed to the entry before
- 03f95092a8cb64d1727801c1fdb572d3584ef4e013efe72e3def14c0f9e444f8
- this leaf
- 8dfeb37d309d3f75414ca49018d0147b9141cf626459c27415b2dac30417f4bc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IvaYefkySxMH7ZJtDVprpIEeGEMB3qFYh84xh1SxMhkxVP3aSKc382kEtgbbTe4m6RVZNmL7ONS3mmaf95BFCA==