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
- b248e200ed445af5e7efef8ce44e295f14420ebddd4be6aa2f35c20bd5abce0e
- request
- 3f628b3d07121e4fdd7fd3e28e69e29ef6452d560a10cbd3575b11c13eab0211
- transaction
- 94dcb724d70b6c6e6fe6960e2d9acb8545ad8f71af91f29da02070eba549f760computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62906
the chainentry 62906
- sealed to the entry before
- 7356eab4bfb3137a35c84c87f620d978919b2b95ff83b6cca0fdeeccfded4ce6
- this leaf
- ae7fa8785a0b8f290c4b6c43834e1650709aae25472fade374e96d051f11a27a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L7+kn7bJB6wJ7ZsKrrA5Vfdao4SHnQY/CnAcoGpegGEMkVf2lJCxUpFIjShLZobctp1Uc6hP5h/9UCAI0yBnAQ==