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
- 6c365e75e9f021f911843fa96b5322631e4ccba194eb88bfd96282f5a5c4aeec
- request
- 7ec3711e05ad0ba3d6101859289ec2c37d789ac4f0dfe9e7dbfb0066af3e364d
- transaction
- bda796ecc7004425782901dc57bbbf174ae7f5cc4d48c4eaeb145acbac83e10fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75007
the chainentry 75007
- sealed to the entry before
- 24ed4a06d6dce9af9932ae662757bd891d0d5d08318ead38e8b42ce6af748065
- this leaf
- fc6afa241159287deeee77f3223e7955cb8d5f0a89457d870728ec65bb3b23de
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- F54qmLqWvg3b+vyAoDDYOfhtvGclazywIrUasHrGoInuLMMuoZ9RI3sAl6ymn6oFq+0hOJgovfal4sZDD+0GCA==