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
- 30d887ce155f480ab5594047681f9ccc83d0ac944ea8d60f1a51b4fbf3241145
- request
- 9fbe808a6fa871263a230274d2d3b42668f9aa6a792b851ee6ac37d437578263
- transaction
- da003690b68bc34a3413daa758abaaa7796cc404f3629c8eb0feb0b8dc3b7ee0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31565
the chainentry 31565
- sealed to the entry before
- 550e5864fb769984f2fbd71f9b1815eb0ca4a8050fa40b22329ad13a4cc6e8cc
- this leaf
- 0484273fed4c8a54b0500369b3f44702f80a109b709561b1e4ff1d512e11254b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- A1+l+RFtmCmYgDgRsE3WCQX1Wynm/U4z4LUk3jmLRrY/l+R6dJkSLZKaJTj57/nUIwhvP1BNuq55k0Anx5ycDA==