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
- dc5eee4098515a0319ab8d68934bf35737adec4d10c348bbf5466779b2775496
- request
- 054d635ffbe4ecb33c8f2eb5c6a459943505c48dfbc9a022ade022a3f2ac5a28
- transaction
- e43559b16d84a9677f8574971e173bf1acf634dc959e1f78eb09c8ecaa9bd0a1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67185
the chainentry 67185
- sealed to the entry before
- d2af9de8de5740bc9c0b8321c9aeeb22b162b39773d44281814980321b5f88cf
- this leaf
- 859f788f0c2b847676f3678191185b15c0792476288a6972e3a48bd6c6344ffc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /wFjtpQJd++ux3TTQoc5LXiGIEhARZdzGA4ClsxwSfZD80A1YgZRMknMSBA6Hon2bQnm1TBSn4BQZU6NxIqiAQ==