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
- 352c06be7584602c245723b1200532a6ab8b4b07d1e43ac089844beb7a16226e
- request
- 5c2bb413999a8e46ef400450d1fa22364f3054cb7b222543ee34590ff9120fd4
- transaction
- 1a33d49ab3fc6aef7f0f75665bb67d441ed05e30183faf2bc6859d46d93be575computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49775
the chainentry 49775
- sealed to the entry before
- 7752be425b4b8bef19c65a406ffc69cee4b0f3c621a3b80e503599a5cd5afb61
- this leaf
- 7e78ddbc8cb92bb235d3d334be65225edb4893881c2b24e347620c8db13d07f1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HlEJjhoIQFpHdh532leWtFvZ8uy6yNxo/OC16iXDrOOZdPXDFSDCH9rZqU2H5eR+5AV2t5LrGJHvltpMcVVVAA==