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
- 0f1588c9db14b731402a0a99a1bfa68aaae453d1cdeab351e9c0b7d58637db0d
- request
- ea7312f5f81ad51fe5fb9dd78da3b3810c2cf4b2c6dc36a3b4c786f219d105c3
- transaction
- a8508997d0b65a92c10370735e076d71c62ff07dcdfe80b4b1c575aa289e8395computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 531
the chainentry 531
- sealed to the entry before
- a14b8939c1b8b877035476009d33b33ab81b5ca1c627e5a39a5fa7ba9d22c757
- this leaf
- 6b9f344a16db0fe4d4e9d3e29faa7d9473e63d5c425f6680099a0c8021f1b6d9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8uM6HhzQVzDeS1mGrHIAz3YLIkiS/wGyE/3Yx3/Cnu0nHJZQp8hhWlMsHhedLa12Kspnsy5g25CnfjqgaMr3DQ==