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
- 59cc2d34f9c487e42a2555e6f270a68f5d7f67d3703ccd9fa362908c3602765c
- request
- 57662337403972806e789371965e730df7eaa1f6197c57593482a116181f2625
- transaction
- 6d617241971fbd44bcca0efcfa6782508a3dc89b5d98119fc920a30015794325computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48381
the chainentry 48381
- sealed to the entry before
- e238a95e2dc294a7aea9f8d24574b4a851f9be937e68148f784953d89ab2291a
- this leaf
- debb1efbbcad4d8b3931a5e235d802d5fdfaefbacaf39920904661ac839f1ccc
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- f3uf/Zxb1oxZi+WS4b9punmHU9Hku2pPH9nB+1/SUVqCMh1I3DwYYotpXRp3tRZP0LUG/852+nWLb1TqP+TvBg==