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
- 78b5027dcdcf63b98073304042aea48f52b21d24766fce52ca56af9641741ec7
- request
- c193491c7876eedb24afabd227837604325407e48250a9e805d56eb6b8349c93
- transaction
- 1f6c558ea1130de89f2153bcb2bc9d6e3af99d2bb39d592133a7f24b414e6adccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41366
the chainentry 41366
- sealed to the entry before
- a9b9678892fe0f8cc1a8074a4824bc22c3895009cd06b8e1ae3f0c83b7c1ebaf
- this leaf
- b4f20fee4a80fef1d41ebce698e7ff8a7a64654f444aa197fa7ccc4489aa7c0f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7ZkprjatbhB1lVjh0iQCLb/mC3b/O7bAsfJrAuZQ3euBYEN9BpGbEiSBc7Iv/mYWrj4VEzD91geVHnkeOOxYCA==