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
- 544ac694b7e933884aecaafe05d4f3a3980201d3a498420e23bdc6ceb711e57e
- request
- 3a967c2b840faa693f9534b063d25aef197e778cf1f42ed7661822f8e85b0292
- transaction
- 660cf64c3a37dc0ae130e58ecea84f5fc03dad5c4b0606026f83b40f339dbb64computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17326
the chainentry 17326
- sealed to the entry before
- 002c3df2ead3c872ef07eeb16489ec9a739b06f4ddda273b59df9c7a39e3b4f1
- this leaf
- 1e12d9fd3258600daa9614cb0f49def28ddd7fc722064a4fd3440b4edc19de0c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eZOUYtq6jAc2Con7AoH/jZqJ89ai1QVdTTArqGmO99bgptkFR9PFYvCGA68MignYeHDY29fddlEdB9buyb7XBA==