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
- 1107005df4245ef901bed86ede3f8d4faf98a6a6a9bc19ab13c48b7fff6112e6
- request
- ee86d7c2bd72ae8b60ede30232b7c0c56bfee7b3253960eb422dc53a8b489240
- transaction
- 9a70bd6cea0c01034afde50e6a6eaf09a20fb62c5c5f9ba59ec84d6919ffd235computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57995
the chainentry 57995
- sealed to the entry before
- 851fbd773d87be24838417eb153b1a1c45f9b0b7cdcf603caf582e319ed6fa32
- this leaf
- 4f74cdd81beefd232259eb128b7dc526b5ac26fcf75ff8cb5a118381c1ca5815
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lpVI37plkdIGpXDPaRZ9z0y3GjIGD9rn9hee4iLNUjBG6mgUemMP0FA8Kok6VDTboPV5fKnENaq0fHRzX0stAA==