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
- c391d3db6eecf91664efbb671d9f7281591f9af22cfaafe5bbaa208699344a45
- request
- c3182258a8f5821f474ecbc629e19a7f6b720f1fb453757f6ae2d835b4f7137a
- transaction
- 96a1f621720d6437bc6928fd6ed3e443b06afe1548a84ebbadda8424e08ec19acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12084
the chainentry 12084
- sealed to the entry before
- 8becd2c298cbf483e12e7e06d32f8621a14dab37610d77623d6502b75a27e2d4
- this leaf
- 22dd69c1e68e3e0a0c411e135063ca6bc8a124e276e7f9e56c4dfe0816716eeb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- USFbyo+5g61DhlUyuQAzZGb8U5b3GfZIjJKAcFY0aVJ37Swv8soW5IYicGb/nfA4IWUjTVCzKA8HCoJMRPdgAg==