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
- f5b7f24462024f0e549b7ddb7b790b2820350d24e9923f68f1bd87173de3da57
- request
- 05737c38416298f7f8a80b8e26824eea66ed77aa2519235744dd80bf00cf6b64
- transaction
- 8802b08ad3a321c1d2d7cc95f46abfb408c694651b12dda4a86fa1a0764d18cccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11157
the chainentry 11157
- sealed to the entry before
- e17058e3414b3be20118ebc7a8d01efb29c2c4078963fe29f86ca4713ae4dc47
- this leaf
- e2549444d21096cb0ce2312107234d3ed2bec84731ad2507bc0a6469a93b2e90
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iCSuyqx6iuk7h7YOzFPVPcWo+YuIigcsau65qSHuSMzUZlhvdWYo9FsFBOZNHggmkScBv2vpk9RFrL5ecGDxBA==