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
- 2fa4bfec86a7449c82b7e16fef6263b3db6abd9d1542cf856fc6522a7a84c9bf
- request
- e5cac76cb7398a86eea52abebd64fba90d38718f503a9ad285eaca6677d5f086
- transaction
- d822a990b366c91cd3c7961c805baaa0e84c77e7526629405cd49ae0e3e3cc9bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31302
the chainentry 31302
- sealed to the entry before
- 4c686b6eb2496d47e73b82bbc342b3da25b714a13bdc225f4f76e59e092ed924
- this leaf
- 2c0bc4588fefc950ed90a96a737af048d0b8fa4b8521d76cba8b63f54a664e24
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2U+zGRZMbf4RbyafmiEj2ed1/uRzGSaCFRyNDu68YarM6SQQBSVraTYH8YwFwZGeegTOabW2iI/oBdZH729/CA==