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
- 55beccd5c1551b3ae27aa4d9e4efa74e246534967dc2778e0cd2d03b56681510
- request
- bc5c4148e80831849e055fe358ebde48fbc24f146accb7d43455cf2decf0bdbf
- transaction
- c5786041d87fa05be8f1749916cff3e27627f9dc8d110748deddee212182c6f8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7186
the chainentry 7186
- sealed to the entry before
- 6cbe7c32061da3fcd3de4b67adf1d9c6f4ed11f241421f39a0a2e1323035c6a9
- this leaf
- 0d824944f780d7951daf80f9b8628c007b1c3722874fb4fd3719dee89524a283
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IB8zAUfMgv0NgLI/PKNfAzslFiiMi2LoEU9Zcp/RbJeDL3c2C1lLDJAzuSvK+XSaZ9Dh4UtJagrZ3eaS2ePrDw==