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
- 71e624b5dad59bcf5dc1fba7c3912f375a9ba292874915787871e4705f01b3e6
- request
- 4b124bb207aa20e1ad587bec87097843946936f673ad0c4f82cdaa8c9b5d0a01
- transaction
- 8597ae4725a4be0747fd3dd1ab1e224e46531f94b1b57b054fa04025db18b017computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55479
the chainentry 55479
- sealed to the entry before
- 15e080174b9377cdd15aec4c002c6f353aaca56723f78fc0dc77bc59cdc08562
- this leaf
- 7702dfe23425749d2aa3cab53d538089163dc1276101db27ab4ca96287aee585
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- X3uaj3nJaugTFzXDEVf9eqIAMrf+6/7cHGQJL/yl964LNElRrLipkq9zEoE4hMZiA8YfCx2j6AwV8ZC+5pTkAQ==