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
- a5ed65ee9c2913c25e380ef50577a820f4da9980c49ead36ce85720e9a12fe5e
- request
- 437651e19a37e5b3c5fb4a96df104fd82b77367c8bc7d1cf72a63b92233b9bef
- transaction
- 0e3d4faec42d32f7049722bb0f048905bab1c8e74facac5a45cbbb76984e9379computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67991
the chainentry 67991
- sealed to the entry before
- 3cdf467910beefa6f12e423a1cbbd6c63de7f961094c8422a96caa818d3ac6ce
- this leaf
- b723a6a744f0c6f72e46edf6d553beaaa8686f57426a1c866ae6e9d949c1fa04
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JwoZ2TtVaE8dgJyDrlW9mlMy0t69aPJfLF+FmC3Pz8VDEjbXohnyVflVhRtkd9mfisgIfSwFVyvezvVe0qI7CQ==