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
- 32c0489dda48771e7bddc9a129dc9d63f1f9157c0412bc0bd9bc751aba1efb32
- request
- d5cffdc345b803091a56199ad5c4bc18c1ac7b9f6b8d78fb21200899f20768ad
- transaction
- 307bb11e2ceeb0548845340f3611958e54b5a7c8e743e0e4f0c3097401b515b7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10457
the chainentry 10457
- sealed to the entry before
- 029b97865c049f8cb027442fd55c1dd172d4757ef84ff6c8f415d3e52a473411
- this leaf
- c128dd3aaa7e7ad9457040f8fa564e03df587df8cd05efe805d59a6b9936864b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3az+5QqP6FjhAPavDrKmoJosyTkB0DI6qjc0tTKZkUL10O5FKdwWdfBazYZKqCbQQ3WCC2iyb3Vl6tSwugEICg==