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
- 28de4fb8900d7517a1ff31b6ac314ab4baec928892655858646cd50f532d5d72
- request
- 31b5ca52b3a2eff23ad82161519b1beeb359fa266c1e1e14bd636b31edeb7a99
- transaction
- d5bd260ce823a5c38b7a07c5aec8288fe4dc29088a10a5cc5fa5e426b9ed21dacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5512
the chainentry 5512
- sealed to the entry before
- 646d7b2cc8cd6469bfc708095f14beb313c981b7865e61b8f7296ecb0adf0e61
- this leaf
- 3e4dfe82d5c7b85fe07a8302c8d066cc3a1eebaf2ba645b3da7d3cc535c904d8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KBnAbILk8SR2qPpg8o/x+7B4rXiWJGIv9K2lMpvxevKEzUQNw8VKgEkFP0cgfqexvgJKVnk+bNCRXa1vmeloCA==