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
- d135f59221d03534661ba96fe02381f0b5b054220feb85efc32d84adff77b04a
- request
- 96fcab13b9d6dc59e667c9c0825f4f447a9cc67a5a4b4cd756d5c194a34d5230
- transaction
- 7214d2f4f57b88cde3ea2a63a440ef193ddab3fdc18fb66d670c1e1353057d03computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11810
the chainentry 11810
- sealed to the entry before
- f81b4e986399feb323e84d3dc03d08a5afbe06c8de872393b65f93de1820be9e
- this leaf
- f3afb4dee51543a3babd63baac0c83fe7660a49ddd1c26b476271871ec36c6d0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Ro0QNvfYwmImjZolP0dFqRphKri7IqqhWYpdTzMrKXU3iD3b61R0/LIC6wsqldaKZRrRBjZSonofq7MHGMbtBg==