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
- 6758ca6ae5234ab09772c298985f9443cdd8d28f95fb4688c8a0570cca4435d6
- request
- 8c33fae227330c26bc3fd84985ef26d44d46744a3f4a516fc66c1a6666bc0ed5
- transaction
- e1b6860f1ffabf0eb08e3e1082b0f48abeca63dedc8014de3fdba6d2952b2c45computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43017
the chainentry 43017
- sealed to the entry before
- 77c33d37129207074a0c225ce4ecbc51c6e3ab7e3c27c1e6a4c13c7f93ac021c
- this leaf
- c5366949022ce180cbd565b8a6492dccfd6adae9ef71aa1279dd76351399ab32
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9+h7EvNrGgcREBjM1kl+VSxoN4KBRte7Tvsp5xr/OrMvlhZo27OIXiNuV2looGEGpvn6VYK2mEQWZTBJqK7IAg==