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
- 93a1be8b5d707b34aefeb5696035096001cd9fd9188f1221afa8cda0f4a13abf
- request
- 48056d03a26db0f1438448f7e687fb76ec842033ac4b9aa22bddd5eba931c825
- transaction
- a4705efa11e38e2b19258e3f301289ae7615f7e3865915d852c677228e6b7de3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64034
the chainentry 64034
- sealed to the entry before
- 8aa961a315a32459e32b6d9e7ba250e394f6f305e5bf113412c1ec14b5d81cee
- this leaf
- 2963ab05fa1a658ff98fa1b8009805e7129ab740d6c0861053838f79744da126
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hgPLc2CqIDoBc4lyq1BaaKyYpWQIWs94FHbBGsDqo7PTdJiZd7uBKZX8xgNjf+L3tp8EPGuPbrg5cMSeWwoKCQ==