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
- f959ee361fa9b7262fbd782da800175907bfe80d742e77ca18b4f78946852304
- request
- 74b564cec015bc431acd60bece1d4ce48d5e2ed0c56f71b1dcaa380ed78a512c
- transaction
- 01cc115e9695d1e51c74a5d60af0f3d9bfd4a899500497165966bd78eb9b80bccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58718
the chainentry 58718
- sealed to the entry before
- 4a646714f9c9b8aa91de6be70dca5d049fd0bd79e222fb87bcc8742db7117078
- this leaf
- 476ec0dbf93421b540ee3340b0e7de2913f7c9c89608ce75203da3d84278ceaf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MQ1eeN0U2Pzd1jssESM7s+pVl7sfKF9dvalOEl0heg8ZUPNB+ZCSwOE4v3FS3ZgCibG8/0UTPYpCCo/Uzq6eDw==