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
- 997a6f7314a239343d8f38a836449341252eb514ed9a64e846f26cbaa1b19d60
- request
- 325541604a71e31727e0f1bb0ef496e2e66f3470c62d49d52750261c75674432
- transaction
- dcad80c3b7db558922a876b14dd5acd77e03347da13cb772b1aa49be8f545a20computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30586
the chainentry 30586
- sealed to the entry before
- 7f5eb5a6628eacbb3f6b4c264dd72a84ed69be26afaacea12bd6aaa05f356ea3
- this leaf
- ee02d7d35d56504e6f0e2f1eec31ab441117e566e312fbef4e8210e5952f19be
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nCmAZEinyBhq2ddcgKfNQJqi7eqOaDjqoHo2zL6Qr2AUlmBK6x0kzbDQn0iYf7QpE5FKKsgVa08qsV6bCiZaCA==