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
- 10bd24249568b274e32b7eb800cd0b6cae82abc65ba63ed2df66b42f97c2ed6e
- request
- 89cae2e7ff6212922132f5b641ef4baf2c39dd3c682a49797eed2d6fa548e582
- transaction
- 479022813ff4f72a9d36996ac1a83edc621b2b508b8a2da5f690b84c15df2536computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19100
the chainentry 19100
- sealed to the entry before
- fb0eb498bc5e30a1e57b64628994803ccc0c0e6f0b474237c2530eff5a934b3e
- this leaf
- 02cf94cc4f13031f679e36ffc64b8e1da2c731052e7a3a1aaba2f1105e3eeb31
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iCmSvh7HpfKreFbqEA8Y6wE6GT7UE5E/0RgEsX6t6egzZ0o71+M7TnbW1ObwjAHwS/wdin7s6JHp4zgj1FniCQ==