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
- a339c9f5d765a907ffe2828c8126afbce85be5055ce784fa82d2417d28329fae
- request
- 55b77c925392b9adabf9052a5c44621babea037905c2252b26faf955204580a0
- transaction
- af6a4dabd47bd9e7d440d8cc9308b390589672d7ab0cee39a4dbf6b5e5f7a3c6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65414
the chainentry 65414
- sealed to the entry before
- 8d26f1dd11410ae886fb9a3493a659521b3d8d732b96d681c128d8e377c16cec
- this leaf
- 3e5afa6166c39f92cc13e440d0213754868e64afa54783793fb4ef452b1bcb17
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WFRmdmuKcifCgcg6+PZqOxrSNYxAJxRgoCCtLHOmpVkgoRMduxMrBI3C+xVEsW9TI0v4ONMw62TsZ5RYKQFQAA==