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
- 11bd453899792da59f57f1e989d69145b3c235fc5e8a2130a6f1d6d464809bf4
- request
- 309f2aa73c5d2e16cf1d71e9e467b95d8d4a89df797afbf21c2ea29be3a876aa
- transaction
- 5098b81b3e57b1435e1dc546c45337a6d64c53e74bb532d1063f2cad806ad215computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56901
the chainentry 56901
- sealed to the entry before
- ab6ed0af52a8277766318d508fa8abb4b9e5d268ed2d99c6458db436b16b8262
- this leaf
- 9e98a9ab53023e4f16174f7a7dea5a7221ef8e6abb3f4465942e4567bf2db327
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Gak2EVIaEXMwPAQ86WVp0YThogtc085CmkVCVqQBZr++upz5gMTP4UzKZGOgJiY521Ga4HvMg3r65ne6tpkZBw==