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
- 0513c0eb6d43e42c1b5b7a7763b8104b1c891a44f80ab5d2690edf2cae666843
- request
- 71db7427dcd363008f69b7c14b31df8a6b4c8b69632f11f06bf35e8cbd69f143
- transaction
- f2a83e4f367ffd4dd685e75ded839cbeac5c3c1859dd7b0d9e1d0ebe4142e5f3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25501
the chainentry 25501
- sealed to the entry before
- 1f7b9a184b533ed1cc86b8620bc3d2667faaa680b51528f51265295ab689578d
- this leaf
- f9c9b472a7b8860e6eabd4fd6566ecf7e0708aed7a8c45625cf7a89c096e0e54
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- gzGVFmN54XlKQrhEWItUNj/+K5TFmaFU86KIs9g4jT2p5hFFtRxseE6i6ccOLlozAHCZ24/eRB35d8WP7tKZAg==