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
- 1a163a2c6c1ee05402e0d34b5146aaf392e5d4e9cd5facff709fd8bbf51e2cfa
- request
- fa65f9c9a0a2db2a5c83343283f40ba7021db32fdf02534c9eb45b34ab9dfe4b
- transaction
- fe65de7fa5454f410e358cd6b9538f1316a2f2e29fc6eb302d605b1391899622computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74299
the chainentry 74299
- sealed to the entry before
- 3985def060f21ebcf1fcdd0400ff09f0f579006f1c448504e9aa1e9202e3c3dd
- this leaf
- 717e94e293ac70c095527f9342615a52dcb4336bfcab93c4fa6bdb455a3e9472
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- p5mN30JR7cX3YwMZ07vug4Iuh5UhoQ4OMST4piFbe8Xsz99TczOWXUYHngbF6JLrsE6kpKtArQ2DpFfxpZQDCQ==