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
- f960f9750949e81ee1518c1256652a6f4eb4b216704fdef6286fdcc4a4ec3042
- request
- 2f1318dccdeb611c09ea4ed672821befd7a61ef9f74f6548d8c0e8e8b602f555
- transaction
- f8a2da76c7ddaac913ee6a865863034506f7890663105cd439192e7f7cd59355computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37158
the chainentry 37158
- sealed to the entry before
- afd1940b4cdf7cc5e8ac132b6da707561a9f03a4421cbb7cefe9ef60e96b66c3
- this leaf
- c1b029d0b75f20145402d095b6d079975cf5bfb7fec6626b3f1b0fcc369ad130
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cQAL0NnMY3o3YKuXse02VnHY60Kd3WA+nojLnd9UCzxm8IQkx8WK+HIBWpxZsWo1vrbfX8AZ8Iw153R2Gu0ABA==