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
- 1f3e50af75853434d8abc448aaad1df1f017000c0ca559e53ac4eecf13b22360
- request
- b6416f247852ca1c5b088cbf7803fb4cbde669a23d21697210d8aa50ce47445e
- transaction
- cab2563845c5c8f1e75676c3574aaf643daef8687d15112141dde6311fec1072computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39411
the chainentry 39411
- sealed to the entry before
- 813fbfd51b054b4a09ce50c7d951393a6a23f14ea3215fea5b8036b4c13a0978
- this leaf
- 16ddc356e97f7656fe29f0bc6333cfe6f6df45a5ed854a17e0d1507cf1a59f98
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4BMieleyIMlit9D4W3YSlgGhK71u+hYp9W7U+t1Bxh6CGWh4lNYBm96Ebvqpwq0h0Jp7tIqIgLdMJwYBFvonDQ==