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
- 5fdc8fe5f2cc61ef315068d37ab4e1ea5f51daa4a484029be469af489d57d792
- request
- 497faa38370e16bcb01bb9cdd1de9473a2b696a91bbbc4172f608426df3ddf10
- transaction
- 7fcf3354e960dd197e337ae11bffefa4a74ed50b4719ec08180d7e9a37d868ffcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49397
the chainentry 49397
- sealed to the entry before
- 8a81344d2f0254fd6a4ff9618ec9924aa778bb58b9ece4cfbd6ee80c4d62acbf
- this leaf
- 83c3e5a5a878314f349a4e0fed2c60c9646b5d3b55c47e8074ccc0c115119e69
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5okjuB3apTQm9SwNw24p+UdFxQkh7KG8gditMpQFAsx06DXbwcxmiF8poDIbls619jpafeVgOO5ydrV+/L+vCw==