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
- 45b1ff742096194a2ecb5f74c4f4936c95b5de1c7df83eb7acd2ca41818f1325
- request
- fcb43558456705473415de41986961a82f0c8e1bea8363b265d97a6293a7caa6
- transaction
- 93aee6aa718053e9dea4fe14f6956c12c508eff797ef33f60425db40d63e7b78computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 19669
the chainentry 19669
- sealed to the entry before
- e625baba995e3ddf013cad3ef4a8b49da48d87b26cc8e5ae0a521a8a24c0fbd7
- this leaf
- c14e64ada1b6b30b93b1bdcaffa907bcc5e05b55129aab741563de4e0326c10b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ud5VY9eXfMRAb+Vtz5ax+jgBGzcwz3FRuNUPS35rCzqB+Va0rDmHPTnKR6cWhbA87/+Ke4BSEN3fOmJIMRZWAA==