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
- ae6101272e73dc0a23581ce5af655869f468c97f89b39cc0b33af31c13c0e47c
- request
- 14e68e1a593b71919cce44c128dc211b4c61f0f2ebc6c153a988c1bc5197289a
- transaction
- df35c51ed236bbcf73c43d3b6a181671580c1f4af91e1ea6869bac520dfe1967computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8038
the chainentry 8038
- sealed to the entry before
- a6b2b9ef3e416cf4153fb345158853ff143e4b47b52e6774a7c29598d3cbbbe1
- this leaf
- 2c672e97a103ca0741c41618a6492270835d5627ff46cdde68014e41ebe93b5f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JzvRpl2yeSmapOCqSijS6bc1I6HDjznz4ApSH1v4zTRiqEHZL4JX/MezrVboChKNu/nzmvkW9A7lmz9qkoNOBg==