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
- a4c30aab5e7f0408f51bc679b035ebcc30a057da6323fe348d1c827f88dee3e9
- request
- 7331b8d280c04dfeee365590e9331bd5949455b6a571d16f78bb695caff96263
- transaction
- fe985b705ae71ee3a7b6813f67aa292065b9c505b2eca18e7df1af28991529a6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30125
the chainentry 30125
- sealed to the entry before
- ea3773eb14bc20c1bf6c1f62a69d6b424ff7db51486e7a2186c9b7292e69974d
- this leaf
- c05b91140a95f9089320985f621577f45aaa8ec0e1427cb8123e4833fdc32f18
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FxDzgjBrl5dVlXplPXm8JuKNXFR4IUnBMxnBW403RgZSgAdcdEBabxzvIIO1bOFExj+0pvcPwfcUqcMW6qc+AA==