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
- ee6e61c4f5285db14cb1e8c0631079b58b62c49521038934a6637d50a4bddf51
- request
- c99e11563265051ca43059776bcc9177f9f2f086f279a9e7f07df7bbf4541ccf
- transaction
- e7af765d17180170c00e05d0fab69aa92be5e9751d6d1d7ef16ee3cc25bcbf99computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74154
the chainentry 74154
- sealed to the entry before
- 4eb720e9a2fc36aa7b55e5836f304add7868da1ee69c8f0962739f22b2c4e1ab
- this leaf
- e74106c7d7bdf7d330ebb85c3f0e8d01257f12d3e7dda048c6cd3ae9699c2051
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0w90cv1tStpMmUD6KRIUtMR5WgqNCsBmFw5Uc/w6hhrnGpr6V125YmerBhL5wQSSkx7gk/GEtEE/EGKIi7/wDA==