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
- 17f904ffd1a526a5d540ecd76316afc931f099767cc80ccb6a6b8ce11c490acc
- request
- 240745a732dec52ad3acfe3969692f4afd11d37c19615f05ef4bee2e78c0aae4
- transaction
- 6319fd5f89a7905968b79e92e960c563f133def38ec6cb03f3d128e7328a8cb2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33643
the chainentry 33643
- sealed to the entry before
- 2549f137b9e1727a6a4796f6cb5994a5fa544ca7fb2eb280c310e9fecd3b891c
- this leaf
- 76df9563603df351229651cfbc369678a4d5657c054a1580659ccf152ebba2f7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mKdahBXkTw6S5JCa8CgQ7hiolknfZsGWcTItYHFc6i396Kl7siM+ha1dhAlWJbl40ECkRajlLlVx5j/Px1BDDA==