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
- 55b9ac6f98c779208d9c4d46b84d4638a71adae88af1d2e785ffa54e99d5cc38
- request
- b7925549798919d71b7b887bd13a3c25d4246b506a5a8ad28e889a8880b7c4cb
- transaction
- f942563dbafa5b6a73fb2e820858716ce12867be76829761e78732105cba950dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40845
the chainentry 40845
- sealed to the entry before
- ddfb7925192b7d9b9e967c1d6f91f45ddc486a788444683a29ffe7010ed45f6a
- this leaf
- d4d40fc1e7beab33031ee339c42cfe8b01e130088a7b4cce60b7f0f7e3838f0d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- TINeyVu4Ag77ccHjW09GIn31dr+iW9m0CPdC3FHJHRmy4RW0XXhkksKvZFmjSvfIB1b2s+OR/6lu9RkWCbWaCQ==