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
- 9e4b6517f9bb79ffafe4859dfa9ff3ff02025fe3c231e9b8022f152ab289a84e
- request
- 1629002eac845523dae0d42cb5e18649bd91d4f2570e1fb49c079e285b57c141
- transaction
- 61323f433830bbbe7f3cf2eb70f97cbd0e8e2ddf5586f7102082ab799bd76beacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13643
the chainentry 13643
- sealed to the entry before
- 9e901204346c777029033045d77d517a722293282299ffbeb0012b78bdfa43d2
- this leaf
- 5d9a35fa44d12ec02e7234f051cb6dfc834ec17a1a29b2a91c51b98936adaa12
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- q/9h+PwgOZxD+iKPPvJqveGCeEqZCH+20ZM9R/EGMR+naZhWskxq5sZzgM5Wr0VYfrnV4AMgf7RnTlv0z0bVDg==