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
- 44aa0d089bc21cb53989bf7cf05a18d631de5eab5885af9516fea809b7286760
- request
- dbc66b537bc9f90211318cc1837f8e71a2942b3fca7ce47a39345636d55f3639
- transaction
- 9070412fe127d6099357f8b00397ff5896b70f1169061cedf3dc649d15a800d3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71523
the chainentry 71523
- sealed to the entry before
- b2fd65dffd09c67aaef2e276ad4560d567a241dd9145837941b835b81f8dee76
- this leaf
- 68a37d3bef93a3eb26d2f42e997706b915e87f3dcbaa9b5238da920ddf12b1bc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +RmpzLaOgno8COwyetlROcG3f7ENmhFxwsZYzh3sRpxi+mJj9TJReh03qJkY17o43xmrbjOFRCgidARFtLUtBg==