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
- e8aacfbfa8992854a2bd648b624617c564e8efafb53f493b5c9a103a62355f5e
- request
- 173923017ecd0f9fc238a60bfac12b8f783a51745e1ad98b024f3fcda20bf14c
- transaction
- a884ea33cd75fa68109cb432fb44d775f59e221805d367a0fde60edac39255c0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43450
the chainentry 43450
- sealed to the entry before
- fe7d504be968ef2cbf13233d9cd88f3cf1960581c90c1745c787a6ee118ae17f
- this leaf
- c5831941969e4107a6900eac6d015615ee8f42a885f2e9b12838f8e994a33300
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EVmOCMoyRnIKRFtVj+2TLLCatMeROZkxoHLKbQ6yt+aio1nmg052WVFHtl2O6uGNfq7KvykLvj8Ztl4k6IaSBA==