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
- 8f067ffff0b09fd29fe99c006eb40fef05d26d5fb7167f2c8e9d42c8c56c1626
- request
- fd65150a2e39aba3c32fa0dc8604b973ff4d060223803c2624e0caaa60cb6e37
- transaction
- a886ec12d98df5a7c34825f8063840d44d68ce60b04c09eccd228b3562aaacb6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41026
the chainentry 41026
- sealed to the entry before
- 4deb5079cc149666b657dc4567f82bf41e2b07565e5e5ef05ee7669bcbdf45ab
- this leaf
- 86b75358acc2bee20969d0c0917eff672702c015134d6b39e64923cf103d308d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ulDBSDwuTdOHwF4HKoL2DwNottefV3AuIcdlpTGHbP5HkfBDy9lNGggPdc5OdOvmGWiCgSQQNha0nXkcZW+XBQ==