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
- 5c9c9e473dfea966112923506c514e1bc265a4c8457e124059b63d5f9d495273
- request
- a265e1b14fa72bdcb099d58c626bc3552b3a9c3abdac0207d5bf8bcdac43b012
- transaction
- a695c94c47ad406966a8a1523e34882ddb1e840a0502d3a50acdf2913a975fa6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36904
the chainentry 36904
- sealed to the entry before
- 255636da38688d3f600930155047eaf5384e78374221639806280e3c03918999
- this leaf
- 594a66d104a0b03259e5fd3ee5d52f8416790fa27062466155fa137024f3af6f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vny4LiUrrsPSGJKquuK4tPC4IOuNxy+WAsquHWXAXx4Tk/y09xG2u2tjiUV2CMNI5i1lA+nrGaq3r1q/5kElDQ==