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
- 5d78878c76d2aa0ffbb82ae2da4534281725f364528a001c8b5dd129e1a85fcf
- request
- 3f0a7eab24bd54cee0b21404884b6b3ef5480d55df404fed8506a3eb3e03dd27
- transaction
- 9acc26000d096ff1130bb8eadecbfc2554484d4ebb968ae2717dd070a9d57e21computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24156
the chainentry 24156
- sealed to the entry before
- d5961414c5f2b897ac63a9054c132583d994e26c61c17b70d1e6b7d2b8063c5a
- this leaf
- b56c6c9348be607e5625e07ee55ccddc1c7d097f841e227d48d3397a554367a1
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- x2gNDUBSwQf/3audmbKWCewntncEJkil1LIj11zJt93tcrbmilopXwcU40UGLemtMaSGUP9O/BlEk7inOZnqCQ==