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
- edec78fedf8dd9fb6de78c7933a384d64d8b1b424abbd47d1ce23b20651bea2d
- request
- 69cd1b91331c28950fd13c5ca9d0091ab67f6bedc1cd2e866be9a00d6a480a19
- transaction
- 33f1563cdda84f67ed7a0631b82127604456f5eb2feabffbc423a6055c50cc0dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68386
the chainentry 68386
- sealed to the entry before
- beacf99411f259b53a9ac940e62593eb8de37461d37b0b261c3b29f2e5ea8d23
- this leaf
- c8e6db9ab40aac48e10bc427e92445d326921c61709c1e6c7203cc4252f8ef94
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HYzT3mKYi+O64T9DILXEsMk/IffvShEhei0i5qmzGkMkUygq/TPep7ef6mzTqoz0qgquz/142+DtLU0ULAqdDA==