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
- be245d1d8b32d2936dc93c2ce6f64d0bfbae783752ada1f93da701669adb3e27
- request
- 5b64f61c4c286f29fae67a7ce590e92e9c12d0cea874aff6ce707c912a9805b1
- transaction
- 08eb9de785c8ecf47b61399f7b1dc8a0fa0e0e4815deddf63fa6dbc90bb61988computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68761
the chainentry 68761
- sealed to the entry before
- 6ab5e8c4751b6fe0cdc4035c12630b9ff365dd7eaf3b95e1f8893192af03b7a6
- this leaf
- 014dc7a92cd20f9bafd97c52b1a93e153a885d3f9a4cdc3ac232e97bdcc49324
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7VbiSqg2SeNer0sEmePopIzzsK1AS4giYzFAQUN7QmXYTZkfXHhyjUckCgx5L0qcWTk43XlIe7a9TLt99Ks4AQ==