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
- cad03d2652109bf138f887ebe16f59bb9130190c861d58c5b95afd2daae4f25a
- request
- 76378852b83908bc9d398df420fd6200aae9aea2ee26f6897fd8d0010c239504
- transaction
- d79a7bc0707036cb862ae59b7e35c93e2d7a7ff437cd41fdbef083a451832677computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52040
the chainentry 52040
- sealed to the entry before
- ebac953743730d032199567738b4e3d51c5ba2bbb3ad5241e2a65c7e8d2e8e13
- this leaf
- 211197f191638514ea61e2f6045bc5e7b30a2736dff2a07544ec9f05ac9d19a3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mSRp3V3iLlI3hxeH8uivt8qcutduFl9GWJx77Lxt9PgF03Gq3h/hpssUV3nCsWT2U8/yjFJ5magDADf2mtbUDg==