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
- eef13b5ebef467050d1648e3fb0eb310fab09dae5ebc8b672f64ff9dd89a0a9a
- request
- fd63e2b7ab8755a1c1008810e5682c2bf1cce54bb335d8f89b4f7b26db6ceb3e
- transaction
- 0fd6645b95d0d4e4f795233e295bed1b44d93bdfcdcff232ff2c5c3117429d50computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7094
the chainentry 7094
- sealed to the entry before
- 7e80dd92a4169a17d854193abaaa9574dd388bfa1823de4da7cc87e6e1ccbe5a
- this leaf
- e4f14fb2e6039257f213393c538e20a5a6690739c36b3434087ceabef6294ca0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3Nr8gchYkgL5nSSaJeIZocS2x1xOgdrvzoM2JLLJ59U2FH5IcbwwEPwkW3cux2kF/xfS9U5AQGYYVx466kwJBw==