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
- 2091c7b69864c650f1bedf2563ff2d1904ed82c6e2f639eb1e17e76fcaba98e4
- request
- 4b22cf168c193ded3bdba2e5d916480cb47a58434d2bd9ffba799e489a6da6a2
- transaction
- d0ad5767474b28909d1fbe91380dd5dfc1b7a3d37b5894d70b2655fb3dfce631computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5038
the chainentry 5038
- sealed to the entry before
- 462e5150a7ffe69188df3449bb0e4dc328600805c14efc2e2529a6eb2e25eb99
- this leaf
- b2321321c7286c235ae157e00a0305871b746f586ff94933361345005ba7d915
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oHBHOaQqDxttDyEDdkdBBqWaFV1hwTc6fDUhwvn6tguBT21rl5m+cy4SDOaszsEzDdvVXa5pFcbUVDP0K3zvBQ==