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
- 4d4590729f2a4ddd8b126d9efd670e5e27646cd2ecf7f25544c31c699b1e163e
- request
- 955450adb47476d5f4bc9f3973f13aa80d4175f4f4863df4e3b2020f776741e0
- transaction
- 85b025db5fbc27a4e4e25774c2a2cae5dd2f0bbf77008bc93310287b16653e3ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36850
the chainentry 36850
- sealed to the entry before
- c3c8f8265f48c5185488a9892eee269885fbc4d1ea230f1327503f6891f7cbe2
- this leaf
- e0a8ad19b59e40a06babf6333ff61ecfdd8532665d68744557dd3170096d2ecd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F2dT0xXCeUNTKSkIiXgwBpjtlyc+WfSkjPkYXNrwc6cSoJcac6JlQJpj5KXwT/l4mpIIuYuNHKjVzv4vbsWIDQ==