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
- 583ad4f8ec256a40831900f4043c9157da151d0fa7db745b7ad049bbf036c8e2
- request
- 7a13cf014119936c86f50004c115974c426e7fe04777f280f5fccc8b93fd1ca1
- transaction
- a690ff69d8b88bcc523c289b6b05e62075f0fdb7e40a2d58cf8936c8e04d1b73computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 346
the chainentry 346
- sealed to the entry before
- 9a69d973d9b2935ec97d457288e92ad28bc092b7f399ca2e3d1248e89ed55668
- this leaf
- f013a1680dc483f7fb16fd4e7555d21e6d0e9f15cb6eb17d7c5ffbc7b37c773d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lOaQETpUrS183iabbjfO6y8lYV8HFn+8dJKdBx1wErDKYTH8FnbL5bz7CNIGeShdKpQi72bY48Tf+wHNa7zeAQ==