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
- 78de961e1e9d1010ffa10d8566b2aeb6113ad0884165f9aa3d81c0447d367dd4
- request
- 45784e5122dd76fc0ae487256663d68e61438284eef8e35f7b0a01882710828a
- transaction
- ab02fd8e3c6be1d1eb27078c38cfd4c7ad5b8ce12e129ef2ae969c4f516b4333computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41504
the chainentry 41504
- sealed to the entry before
- 414dfcc27b1827a8902e2550109dd1e7a0dba68590b0a892305e7fb9792f5e47
- this leaf
- a9f3f533797605ce846835a804a0c32cd770cb5f37d870b2a7c84eadd1d341f6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xMHFKOsohg3pDRQiC6IlFhmuEQC2VrZmCKgfqgIcTYzk2yCMqgRG5VArc64+fiNGo128TOOeXelJiM1NZuPMBw==