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
- 090e486202685016a39489cdf8d15178bba42c7268b7dfc469b19254cc4a6d79
- request
- e31926a5c95222e5209b29c3c9671667e0d4b27cae5d488d32aa1acd4079fd5b
- transaction
- 74d343e6d2f8ca65771a81717d11911fd64ea1d7e1464d25316d859478f9c615computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10158
the chainentry 10158
- sealed to the entry before
- ce4b73ebf29cfbfad3208f8d0d120d896c15e8cf75941b0fcd2751a20a49baf3
- this leaf
- d8fe598ba0ab6920fbdb15264e0e3f62e6a995461fa8ef1c4db00e73b03ed86a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- URRuAHugRHB3GDxm0YtYoC/QqhdIzAbKwysT6DAekeOf8IDPRvmZJsfiL+rmXDaP1TkN/O91HuqP+mx9xsTSDQ==