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
- e5e525f839b073c789de3d85e3063cdf8d4555d926c25664383cf2fdf4829821
- request
- 21d547fa06632628f1e99966f3285fbbf6c8e9b11151bdf33ca379bd08a8f424
- transaction
- 68ef3f1bedc92b4965f425e3e337845ff2980fc8eae78228a9e100b14e9980bbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 641
the chainentry 641
- sealed to the entry before
- 1d28b101088a0f4ed6820411bb35bb656f8322e4d4adadd956046840490acdb0
- this leaf
- fecde5e91c3381b47a3a407c3885c219eca29861b907918d5c01043c8aa42a5f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5Y3qpNv8btsCf/XJUqCKJTprcRyUqnBGzOxU5pPSSKFCmFnDUGpDg7OEvejBFExgsc885+FCz4o7CEsv4eEyDw==