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
- 5bd511181511eebc207cf2b510f7fd0e58f761e4fd7523cc81f0948c9f48b5c8
- request
- 479185c2ec1720380fb2d0a2e33faa58a3cb26d04c14f7a766819a72e0886e17
- transaction
- 27b707b49111f6b242641975555c27fa767d2fd4ff5eb670315d5d2798a53ce7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56353
the chainentry 56353
- sealed to the entry before
- 5125fdf12bb35dde67ed2c1734cee71642d7fa0cd045e54ad7fa3ae66d1e3337
- this leaf
- 9bf7bd06b50b45d851ec0c5d4d3bbce1aeece1ee6b16b5d86fdc3f62bb7bdbf9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BTI8bcxcMYP9LKCG288BqyznzgB8yAvpyGjsSS8pwwktPRkCcmNZJJ9Tu8TmAkZpKfAYMd8f8wdYWT0tZXqeBQ==