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
- 71351af79dad0ce8069f726aaabaa117359762a13ac35e34fc980f03e401aecc
- request
- f2a9769e38497c6f45e151e0831aef847361f946069b536758ada434224ab054
- transaction
- f0de58151f6cef26486f3b15308eb4b174551faf4a6bd9a446ba82d02897df76computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11775
the chainentry 11775
- sealed to the entry before
- f9c0dc493c28ad669f301949d9f03c3d7b3a156b3e433b9334f4aee7cd7c3064
- this leaf
- 1a8d8ac8214cb1790225cae253fae6877e36287d8afff6bcbfe357d17779d0cd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- v4pAwbc1uoHz/W/KkFUCQibCYYmPgBsscmNqgQkFao8duopR6YcUaC0gfn395BzUUnLpVNbTLivv02mg3l0dAw==