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
- 22c1dceb3f7b979790a4de725c781f5d54e27bec8be302110b5fd2b65d06b974
- request
- 0a2973de52ab767c1bed7b3866f51d2f672e02f283e67bb2b163b1b3842a9249
- transaction
- 222393ba0414b85cbbcc62d4700103321582c93966eebd3b8d65e0cdbf8a54dccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26528
the chainentry 26528
- sealed to the entry before
- b437997758a3653e311b33b6d08f28d292fe519dcb76d2a72603895b893189be
- this leaf
- eb725778412a256fb43b3a2bc746b6efb46689a6a050dd50f0b7b3910a3fa3eb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /FHoyMIh/YwKws/Mz/cAULY9leRgyv9MbhKKD5Dk7hP+DVzqTjB6vZmmlKleEeshYbkSu4Nzp9j9Au84+tnkDg==