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
- ccbad581db4f2f59368060d73fc09fbeeacd3d8e53f59468ff6b40fb5c63d4f7
- request
- a2b7a87d6bb7db435fbbfaa4967bc4033849f341ca1eedc5776639685d7cac22
- transaction
- bbc44713f31e209f93febac25e2592ea707e284acadd6e6d72754f287dcefe2fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1450
the chainentry 1450
- sealed to the entry before
- db2a916cd56e6d3ecda3ba9a997eaf98ea4ff60b52774380d4c6eb940d26032f
- this leaf
- d039cbf6b614ae80945cff0a78e5e57421c4dd5f80b72c3337597d6423efd169
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tCg1o03rV/A3zMG9u9ILb2LUKFCB/fQGB6LUYFNPmYf5TJJdH6Fkc78PeAoY3TFccLj5zozN8Gpk79gh8C2WCw==