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
- e96e6bd9f57a6b572b6a7a3b147934f4e55a70ebcd43db1edeeb54076b9f3fb9
- request
- 687ffd2a2d3c6c152fd51d4444c967077753431689a95fb62e4a1b02fa1d31e5
- transaction
- 00c6510b316c28f3821d08c1ce892b76237473e3d357f3ba976bf05518550036computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49619
the chainentry 49619
- sealed to the entry before
- 70900cb31d3ca937620b912f4f9e22d00df95611cfaf1500949c287fad313d69
- this leaf
- e7de18716bf4bf3f8dc605c517811cae98f2394d119c65c7946d0e3ecaac9951
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ooSiawNm5sGmnyOiCmZapDQsHfJMqexhgDnWs7vFJp40veuMSjaONp7ihuAB65FOWkRsl0DZ9kmLUN9XgftUCA==