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
- 1a4a0df41af23d56652e6e1aae4052a157c395b5923e6ce22c4c19b1961f4344
- request
- c51abe5e4ef0bf185a60f3ff635456914cb4f582997897703604776667876e4d
- transaction
- ab13700ecf743a42b73dd80d47bf3d8837dd18e97d3208874ac92c41932a8e94computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25088
the chainentry 25088
- sealed to the entry before
- b79ee2d1a0f36bc41f9fb23f74454523881277ddbb54bc45073a67bd181fd1e7
- this leaf
- baa46ef573371e269f7de792a6f89fc3a94ba213178c8dcea54cc1cca7678552
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GzfLrSlFjQXB+nj9QbUegKH2gyG6I0+apPnGtuGE4nE89XHJad7Vd1r44mx9dFyo9RVCC+JRXcmDRM49L/diCw==