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
- 37b1569c3c2103ed1beeb91fef02bf2a17e64fd78d69257112d866f0ce12e5b5
- request
- 9bfaf216e28d068d74df22b4a364de22a3893c41421c0a583a99a0156ce8d326
- transaction
- a4e0ee29ecb2ff83d41fd7c3036ffcca27c73376e039fbb20efc07bb48484672computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16755
the chainentry 16755
- sealed to the entry before
- 77075d8a1e9789fd4af26864e492ddfc353c3d0e941c8c2fd16441f0ad04bfb2
- this leaf
- 0c0b16e1e0d9601bbbea8594726da21dc28d0a73f71fa07cee13778fa25194ef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ReNFMnvwbxVuvbnZIf5zbbkwz7nmz/TWvd2JjF/h24bndaqZ471YIxOVCPXcjqqGh90JXIxUP8eEAAv1mbtwAg==