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
- e0b3175a08bd2ae8cdbdca851a03958269e7b3b611a5cab0770604e653481260
- request
- 6bc835573a58d3951d3095666bb85490f70ed7a3f5c75793b6d573e655f4880d
- transaction
- fcf94e944d2d1ff4e0c7b4cecaa503add3b455bc13fa55a4ad7fdd3b54db6e22computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56098
the chainentry 56098
- sealed to the entry before
- dffcd366dee3f1f750861a67ff1ed1820fb0f6a622027e4f244d8d5ca4fb3bd0
- this leaf
- a2d86d6e7a27a5e0c221f3309d29a2a6d5e5c8d9c1ed19cc40b6d0f2740bc126
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0OyH1sY71JqyVGPuSvQ++/q/aZb2SD4PbzBH2vbT6+1CyhCCpjaR3+C2zzbjQwA6B8R5DuMXoh4rS//0k8ZHAQ==