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
- adfd8197ff8d1b13d8d359dc9a09d43bee5037045943bbe2e2898366dc1bdf00
- request
- af83c5fe321c2916607b89b40a69894c3d7e56aeb782831e1fa0eafea699c541
- transaction
- 1ef72795380cd542742664e321ff2fc1885baff31253c179aae48712eb5b9ac9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34903
the chainentry 34903
- sealed to the entry before
- 73fdcef4f24c1df474b165423abd9a2ba2dcb5a7a1b327e5277c9ec6f0803068
- this leaf
- 9accb399404dbe925fbeb791fdf3d6279659ad29ee483bd4a4e6fb7f5cb705ef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NMff7mvwI9ly8VoM47rIy43+AJQ61uZcZGrDO5X3fD1XR1hEzZ142hIDfAvW7F2HpbFnUPRVBZF7kMA8PEEZCg==