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
- 93afd37ecd7d6147f391435032b9c9204f5e9b075eeeb125a43ce2ae60878331
- request
- 2281c765aeda28d9044eae93753cd5833a5dbf998dfe4986ac6dc3f48988e23c
- transaction
- a3ed21caa1c1f4241dba59a40de9a35620c37db85e7fb94a2ffe31143d513681computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60771
the chainentry 60771
- sealed to the entry before
- c007c8a7f203c0783301fb37991c5e7de37847951d26dd8dbaa2d51e7d8e6bf8
- this leaf
- cb51dc66d133d7dc240d894fc147b4f865aceab37be5718e101da78351626a3e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QLdHI1BwDMPo06IPLB/Vw7is9/0EP3Y9fYn76ieg62SbhdxOg2CQHmEaiVSULxoQpt5aiZgb19BsaebcZZE7AA==