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
- 2620db16a5be1cb8b8a642e4da16394d50acaed149587394c33c3bf621161968
- request
- 95ea7af6c6c4f222405d944f419d2f626036338f01bbb7971cfb67ef2ef79690
- transaction
- 7b9efd4ecce47d6aaebabdc906b283596b9d8f7aaf03affb2b2037c91ce7bcd9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73851
the chainentry 73851
- sealed to the entry before
- b59691ae0b781ecd66deb75e674af319fb4c0e293abd2f5207748a4164fa0582
- this leaf
- 805ee43dcc759259fcdddb05c6ba33061935f4daf4da60ad48acfb5fcb688637
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6scqekA0WTbrBT2nBjYIFcTztAlpch9YKmHsf+R2WKhr7u7uZxobby36etDkTH5fTl8eWCWfLTZXC/nMJgnOBg==