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
- 1bc90715ab11baeaefaa33fa90e67f591e03fd5d4c2704890849557c717a85db
- request
- fb42a7d46f0f884c62c4cf580205f3eaba59e7785f3b4decdc991dfa09e6ee45
- transaction
- 3037e04e07bd73ba10a78f8011b1e1f9e4514f0fbb6d0fd0c9e8e6cae10ec433computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72740
the chainentry 72740
- sealed to the entry before
- 15f8fdcc5a5860347ecb4ee3b713de569d23bbb8d64cb5c7de36b33a01f3a355
- this leaf
- dcdfb2fced11d5125f59f3670f68323cfd8a837bc44c5eb8378acc47e19a05eb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Nh48D0CWJ0xYFz3qdApnIXMk20DihL7fXRgZrGTqVoKm1o/O9CuhzwIfbFxH4Erxw+nWZ7sMk6H1VIYY1qklAw==