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
- 254c1c6eb4c390f41615e405bdbbee0d878e96a66a029b3e8eb9599ba4284e7f
- request
- 40200ea5b2601bbcf6bf805479cd07f6c9334ee63bde4a558c041e3bd3133467
- transaction
- 29a822471dd4411329afe270015fde412c2f90de34d1c7d12196ebb3a8a17b3dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29667
the chainentry 29667
- sealed to the entry before
- ecbfd36ae7c779e21fbbecb90cec57aac8227c070c88b15a9738dcc17006ab09
- this leaf
- 8076aa3945a7103d30b908d2122fe0105697e57d53b176eca2c9273be60ff33b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0rIyXfMhKFBF4gVETbs3tT3AxDOYfgQc+V2fUPxjzby0vEoZXYFnOvztLF110DT/4JDEIOrL4Cze1g4FcxoBBQ==