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
- 39c6bf85451faa1a4b705030fa3d935a94fa0ac91d11845f63be8f5032746c74
- request
- ccd5097d0d27697a39f8577759d33b4e8c9fc58b6d18ee143d9df95b03f88374
- transaction
- afec29d5bd593eae3f6584546de059c5ff91b50011cd4b987fa6db946162a01ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76073
the chainentry 76073
- sealed to the entry before
- 423cae08baf105ad8a1772b4486b619e3d7c1bc91f82e4f920425156018d3a96
- this leaf
- 2d49769a1180f7522f09ab9ec7242ba759b39b316aecd287170c1658a9f0d36b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nsd0vZhduLvqYnEiW9Ug6jPoAUfZq7kdxzLuEBIF48xts3ZJYINVmyjwtHeGZW5z0A/3Z3an8pS8YfzUulKRDQ==