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
- 8f97eca496366f0c7e8575f47e69619cebf7ce71d1c68fc49e38d7f7a20c64e1
- request
- 865dcebd8ae9b3658ca7c1ca8daf6b3fc4822230841e5cef9005176db5c53eaf
- transaction
- dcc4f1f2e27ea1ca5ee6e25f70674e5285b58730611605efcbdcc33971875824computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 176
the chainentry 176
- sealed to the entry before
- 3a32b5dd03e64dbcd88200e9a7fb9d0a8c3c121e6b26a457799aef812ea2e144
- this leaf
- 836af40d6d2c857aad450d6f2e21c96600156e895e518f8c07a3f6d5f98da11a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0rt+WJl/W0LEsTHwnlRovhCh5p056Jr4ngmqxK/QRhz2kDcga/UlGgsLSBHsu11riyeX1qc4E66ma36+GxHkAA==