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
- 232256a22b1ff8c33f91bda03b5391094bd3548cfea8f398583528223f5a64c0
- request
- df8b0c6a7bbfcca52b056310c7d1f44126ab25771fc39414939975033efb399b
- transaction
- 198f528039fc46c36e9e64bef549dec54471063ce5443b138e92e687dce0be92computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17590
the chainentry 17590
- sealed to the entry before
- 97e34d50fd368abae3f376f01f43764f39a0ddb7b935c56f4e856ef750d657bb
- this leaf
- 9933a8d3a557200698cd329169dd5613bee339909afcb78b190f4bbfcb9be2ba
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X6fuLBT7zAOTVsy7vBnjofYDA5jf5LqrM33zQi0bR5TCRS/spmjMqBlxqmGVKrzaV9sygUGKrfSWSQzES018CA==