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
- 04dbf4058443e53151213d886eda299d65602e11546618b55f8b84df3c310e32
- request
- 2b34ba1f9f8cb4f3f5de2836b3cb3e2e6a1c184819aa0446ec7ec0e27cb6d1d4
- transaction
- aef37d8fefeb5bfc3f833acdb4e51b72e3276a400dbf85dd016f838e0413244bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25635
the chainentry 25635
- sealed to the entry before
- 40d199214689182bbef6b9794b38987a64eac5972a73f3c8300c4700e99c0556
- this leaf
- ccadfc82cc7a6b7bd131f2a17f414aa7dbefbb5a20e311dadff414608237c9c5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Siq9Wlg6H9A9k0bnv61wS/roigZkR7Bcia8PfunliOVQnIPMA/cdyDdsNgFVRJ8kZRUTnJlsBoOjwXHOpYZFDw==