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
- 64f51a2ecce6a7291cead74dd324029cd0b9295cc2c44ead7494ae8d0be48688
- request
- 8500a2ee71213a219736e0fe08c97140d7c4cb9bd3764bea2ec829bc88fe9214
- transaction
- f9555265e34bd2158ea20ae8a352624387081515def338e56b76ffb47de0dfd1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56965
the chainentry 56965
- sealed to the entry before
- a78ad461dcff5316c908f3df048674f083c74b56ffc87caca39512f14d99d6a7
- this leaf
- 1f9af58250cb804476110a374fe9fba17888e070dde5e771491fc9770d8cf750
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wDIg49HwdQA2mxxA8a2BkTO3O1eVtyIgiAzpgV/Foh4mCgqYnP0/9mz69t40H3Y9LoPLpgkV7t9KKaUiC6bBCA==