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
- 03cd57ed642017c82f10c22cbb6dfc4750e324fb0465829ad0658c9e8a36eaf7
- request
- 9cc3249072787eb7c8e5afead61d658bd7fea8e131560e19d0a206fb190948a7
- transaction
- 500f201571ff7e9f75596633f175fe4f0b40b55ff32fa2292b30a545d0ed1591computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68732
the chainentry 68732
- sealed to the entry before
- 7f7e318a68cce8618dad5bca2bca3a78a04f9030bf09bb58d1c0041c3ef653e2
- this leaf
- b1a2e96f075163faba3855d54cd2ee05c79313882233604fd003d790adfce9a0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- WpGdY/08Ep5jIkd6sDsxetcLzDNT2ngg03265J1KZyBsoAbTFSzCZg861+6bVSbi/87n7OmZaGmtgyjdpV+/Bw==