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
- eadd2ead82f88cca3e122efcb8f9d850ef7bae04db588dc290f89c12eb5e6aff
- request
- 5a7a74fac22f94bd6e1bb57afa1d41a6ccdd745096d3d0fe19765b117c268bec
- transaction
- 4c40cec6a2394552453b0a3c1ef2a6dc22b3c9854c9fc4713f82d97a00ae7360computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39420
the chainentry 39420
- sealed to the entry before
- d68fb9762a15ac1ff6b32e2643d9a599c76b3cc6f2fde22332a8317e9e86dbab
- this leaf
- 0c8210d7ed782766e0b3efd91942d812a1d7941849e0a36826d7667ff326d771
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xrn0SRFEgWXaM646h+nO2V33M78dnJWwD3EG0jhiThbNiaZdLj85Y+lOohNcjxON9DRlDqGpkQCtLwGUB/RODw==