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
- 8d6c94ac995fa89466052b28afd73e7cc0bc6c64f955d860239dd104ecd4a0df
- request
- f80c2029acaa7ef2d2bf54216fd949d483f322711d93692522f3ead2708955dc
- transaction
- 1a9bcf63b43d3731eee2008b346efaaa2e2be4b8b341065f4089ebbb0cf74684computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 53436
the chainentry 53436
- sealed to the entry before
- 61861ec89388bcdaee14670a4fd9786f0ec1d0c5057bde4c55d918d66c5e1111
- this leaf
- 11aaab73d06a500ea7f585a5a0b4ad132669d111e0307c98f4c8291f1d9eafb6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LTlv2ApYpnVrTUJGK/LkFfCUWun7K9Wm02NVaGqHzo7SQBqbJhD+r0C85hiMc2zA9CDYB+jFEKpZvR4RelUVCQ==