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
- e65a206670ceb1b35889a2c8a127ff5d98139aed6704323c83297ce1d1668932
- request
- 64347ae03027ee0195352da3949db07d8d18465ce827896fdfc4008354178930
- transaction
- 1ddc5e6fcc752bff308b2e24598319f49b7e24954fcddb9e0452d4ebbe452f13computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9068
the chainentry 9068
- sealed to the entry before
- 4239b353b25d2bb57a3dbe65d95cfae04dfc8bca9700332952e73347fd70b7ac
- this leaf
- 343f9465a56d2f9318e61924439b8dc1d307b87da2a3d0794300d25c6f885398
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- osm2MOzJwXTZHTXkq0ddHbWke6IkSoq2PbkSyRsOJex1IGhaou4Yv+pkYUBCfbIBL0fKFavL6j3u3wrQlVs1Dw==