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
- 2df60927fd9c6bf590b92c9418bedebba14ef04d68db9eda4f94dab71caa6466
- request
- 366824e3c08dd7d2ba315c9ed19d4123e6658028183b2e693a33ec4847974fbb
- transaction
- 79393b0533db6f7862b66d1c813f2975e0a2c78191e93e1abd49eda9184205f2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42586
the chainentry 42586
- sealed to the entry before
- 774f7599caaab596e579e396e884bd2cd4cb8efd075391e68de50119776713c9
- this leaf
- e831f0239177b6c8704ef044e9e70e598b76b53156f20f03604d838e4ca26795
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Fwd0bDCvb5C1ofJ+8LMUTdkv/7TfK1iWWBsyoRIMgJauNu0/mVM1vuyzxWHzu0OEJCy5JvhV3yIRH7PfTQxcCw==