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
- ecb9b2ef8c71eec0051afe2a34755e82d8218358dbbfdd50ca7cba0c8a909e32
- request
- 8d56250cd60357e5522fb1cb446d47d86cd437c8573a28f214b7a8493721348a
- transaction
- a7c4fb6658a68076721f48b72fea2463e8d0d39c5eb2e560a09465c9ef526d2acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 861
the chainentry 861
- sealed to the entry before
- d41da1b66cf1a3eafcad910f45a98e09d4b89f11047aca706284627e625952ab
- this leaf
- 72bfff63349eb6eae7b9d7daa9e9463341b3520c910571f1b9bc4b1375dcba11
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D0v32DifUzCcy1/UmNox4NW3LGdlQ4uQ5WT1ljkIORmTg/pTpbZ60rs2wQc2ybGYPKrw/p93K8L5EpUZU+qiAA==