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
- c6aba249b71d7d5f4c0db979712ad6af1455f0eb74e2a5519091dab73710ea42
- request
- 765de192ed1b367cb356fa7520f50aa803da6a7cb427fbcc9c6bfac9bb1d7890
- transaction
- a625775197ae57403b2ae31157ea71ceb103253d6f2f357698d43d1dd7f0fbcacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33373
the chainentry 33373
- sealed to the entry before
- c3bfc4ea9e687fd508afd9c7e0b2c63d512ce6e6eb5d8cd1f965805306922d67
- this leaf
- cd0f8f667b484da25f6bd53284b7af780cd0aa455fd71ce64f9d35efacc1983f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tLZg9hWYdfil+OeZ4bc9uAIVCMR0XXlQwWDniHrWmQHYmtBkFdt8vxqFzOC2jgV8OF9eyvrhcfgGgT872jOXBQ==