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
- f82c0f69c9e0b805a94deb1a510f3c26ff402e5511cc2293e25907ba9fada85b
- request
- 8d7ce4ee08b3b671a812ee71c7832df011c0e84d109266950ed420640ff11f85
- transaction
- 3424084312c23b8c9b68a5a5fb1648166a6899fb12a7a1ad4cbcb6ee29753710computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1028
the chainentry 1028
- sealed to the entry before
- 789d1816f2c931e87158bd4a31c47cf6c9b48394ef36a5a08ff1e54a4aa423b3
- this leaf
- 103b721c7c8efd019b2ffe49d0b120c98e0bca9edc94cacd4813b9f2944c5e01
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fn/i+8uH/kwHt52oy6u01uT53ek4Z8dHDgqLlljYKeRAj9vt1vlpZ5QZJt24qhekfgOzGAFd+1yq5N6s/xQrBg==