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
- 6a8d65edeb9c5225bb3d30bac7910b9c98f7f07d8c86c2942ad76e4653527d58
- request
- cc72578ca36cfe36e9f937846780d32862c95f79cf02bb5073ca064cd9d7993e
- transaction
- eb6a6c4b7ceb0967d55062121f7d47ab5c032e6009b526f0a57eb901b83af5e4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37959
the chainentry 37959
- sealed to the entry before
- a0ab5e8e9ff219efe328859c209f2691261e867ecc10ad274a023adbe681dd5a
- this leaf
- 05c886a30ddd205a3df7e4cbddc5957e582cb139fed0a6bbf2a89a1929a620e9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ih/Z6jIMBwxoxVvAFaBC+faXhwhy9ZZ1jEyC3yqKqh2fmnLc8cSAS5arwjQ+nnCnFks9ipdHMacsx1a8EjgCAw==