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
- f87d4cc44f878802f2191974e1f42836c984e367869725cfe05643f8f75b3d88
- request
- 7f55ae9e79522179399d64d06b832a866d4a46749b1a5b7f8d6756e7163a1d71
- transaction
- 49af3f361387cdfb98aea9cce167b6fbf85d55131fd2b4b2bd0911adebd06d30computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62212
the chainentry 62212
- sealed to the entry before
- c47dd8bd0a851657c406a38aabb3a43ddfe688c0dd7e55fa45a3fb842758ed7c
- this leaf
- 71bb7dfd34d272f2d7e080bf90fcd94661c798ba773879393f34e8f4e33dc021
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GqE/q8oT84ikvaLI5Dq2KCuR3F2KOUbGxuMoyg8mIyIuBTNJBb8moD7momX45OVFK7OeYYE1PG6jmy2eBSNBDQ==