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
- f74b5fcb27db66e358c04ff4c1e7a20e08de9c195228720d0ae0253cd9131caf
- request
- 6a0153f9aba251e6a550ed659a1de0ba4fd45a0e12b5b9857a61ec5599eb84c8
- transaction
- 72c3786245164238efd642e3a15df558ca16629cfa1d7718a3b0c604adfe3e16computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52056
the chainentry 52056
- sealed to the entry before
- 12184c3ee57de844771b4916f8a90f25ac63e43901fbca79b1fe3095f8dd4392
- this leaf
- ab23c61c95160aac33ff661705042baa1d01e2e010759c30ac3f216eeca05a42
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uLDw8+utWqaX75LhRgXr09SsTUxW7OaVfCXuyWhOEt8wcSlZWBYQBVq43PU9R3eVO0NJwGpdSRCs/wwbnPH3Cw==