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
- ec2b97f84065e79282612f9849b89ee57d15f846b6886a4d09a4e64a6f0de69b
- request
- 4073781885775e757cfbf101003dd9937b804066afdce09097ca434f9a549f06
- transaction
- 4f5b49883379e95beaab26031f68eb1fe28d42995a9b556d1feeffca62b9c52bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36221
the chainentry 36221
- sealed to the entry before
- ea48e56b2c1cf6ef131889607a306b8c542e8a4dc6517958d99a306360bbe5f3
- this leaf
- bd1e271062b8b37b4f94e24bf46982db046c243e279c880647bd61f90c16bdd1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vyrRTKoD5JE51UM3sYzr3R2h4wPPVwuW8E3ZXH0xPvNwEYfmiDVSNCqmKXxOKBn27PXN4l4XUY587jfegcvRAg==