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
- c6f104f3ba7b8ceb0e635d822a11e08f43d965d65e761ffaef9c5ef3301ac300
- request
- fb780bb8d1878e7a5ee9094c0f7bf52ba3392d6dec434885f4a1a781c410ad7e
- transaction
- 213dff47823b4e68aeaa29a4439ce91da3637366e4adb5cd9fdc6c3cb79020c9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8977
the chainentry 8977
- sealed to the entry before
- a6e376676d7cbb8c0db5504addd92a399a67ab2003e9914d3653c927213ea9f1
- this leaf
- 186d4d7d4e261859204575efeedbb92d619cd8bad7ff677e2fd108c2425e9ac3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dDKFLO0px8rxXpH/YQbC6QBK/7R1l85MUwsv88J4tOaJqTsxZDzMUdvlX67ssDRaqqmRGCtJ/8htzhYjAkKHCA==