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
- 2d450cfc598aaf7e5fd7f57c5f0481257de548dabc08cd7507e7b66c0f3515f8
- request
- 292cd5ba36616486b9ece4e01ee703aad0f072308223c3752fd3281849a22200
- transaction
- 7a642ac64442fe0b2b50a551d6aa93b20bac1c4e13156e1ffbdbf08e1b8502dacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69060
the chainentry 69060
- sealed to the entry before
- f6c7fce26c338fbb12d04d7997cfc1347d730a94a04cbb1b2c862e564b534293
- this leaf
- 6e179d73f277edc4af1fbfc3216b7e41c000b3a93605dab747c07c45cda78fd9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9zZQu/TcC8xJtBXJjY2zJ1Wh2K/LelV0CNYR5MA4j3yjEiODC/GeQp2BsWMVdY35b3JnXDgVe4ImT+qAIygkAA==