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
- 53e52883b08d90658f2756df551d210492eb3d4f4327051ba980d96f25621ae9
- request
- 8474911a55bee79395003d1c38f490b312ee2dc8bd91b685b4a57d1dcdbd1f31
- transaction
- 26677c3674444e6a8ae74872d41474df73ba3d88daf14c58302e474cd4cd2350computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42204
the chainentry 42204
- sealed to the entry before
- ca3c965dcf7c549d587ddea9ae4cd735490fc224304044a0e870b6634d5b2350
- this leaf
- 724d58c85aa390c2e440e0dd0df648fab5ad8dee4da2d5f66d23fe4456bdd9a2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2uhEFrTs0pCptz9fn5FtV4LiBNdYI/XZOXFMbTau/HGaesNV4XhXzWij8GOCY/CEbPaxPlQnsiOQfv0lrnzQDg==