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
- aa6986dca8a23004681143bd6f0931002a1ef46836d862eb05a7aaa3f9c6e5fe
- request
- f1d08af65d9441841ec2a4e8eeebce9a51edb96931b41c3fc9681f75bc479ac0
- transaction
- cfe244303ae7a0419bd813d6b4ab645cdf38d869824021f1108e2ba2b6236437computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50019
the chainentry 50019
- sealed to the entry before
- f4b6a9654033434a8cfd54f5c2c68df6bc150dfcc8d7520d8464c9ed36d4d31c
- this leaf
- 7a1401702879582ed2aa2239dce7fae4e977e1d0c78389859a93b770240340e4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fcD7Zp5j26TXNwLsXseDlLOWLy3hqX4izvWPqcCvEIMrqWOkM4cjeyOt4UQHPDh3AaQ5A+CxVqX381kyj45xCw==