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
- b9632f52dd77d8afc421a7d90deb71527667c6e1a0fe1c379c40878acd95635a
- request
- 8ad4d9a75db6f0681fa1284b5cec8dcb603cc9575d73fc5a7ceac42067d4e477
- transaction
- f6b186da700d14cd4be5775ea5afbf3a21cc6028a333db8574a1d68538ddef63computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 61188
the chainentry 61188
- sealed to the entry before
- b0718669e1a375724e495d45268cc4776a2f8c4d8a5dca2193a3279deaef70bd
- this leaf
- 2a2383489d0ac5ed4a210547b2ac39e272722e4a9e21b7b839446a04b64aa512
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bKiBxydAK03UlIriGh65Bp593FVMaGqv9gEKxj+AnGzNKODrJBfPH5Ouwr9TfwPdAUG2UxNQYBHqGfn8DFHWAA==