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
- 79d69069fa6268940531c1b7345e6663d579cc4f16952824ec6f38892b648140
- request
- 34e91b5e7eb967eb9096fb23b9ab8c0f7cf2187521c39244bc71083afac01002
- transaction
- ff0d952503d68dc54d89279ed95626b4b862a278eb27589f48fc06acc527a6f9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16989
the chainentry 16989
- sealed to the entry before
- f05addfacf5dcf8e93b638ad9be969bc78120ccce39a50a5930a237283cc9bd1
- this leaf
- 2da618ae200935bb7e9cffa20a12b1bff80b7c63d92f1e4ae2a534e2cccf1bc4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /4Y9M/CH8ZXIEcefT9uE1buo8bc2zcS6tonEpQlmUyz+GK+M0af6+inUSrf19WULNE/YMG0lYu0HuIcv4V35Cw==