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
- e7b9b0c9f33c36ad65b6481895e82a3f8a1ccd5951cb7e222479790bda5fd1e5
- request
- d8f59670d6313c75a4d46e9efb282a6334aa2fa91ea05191f84d72e8cff113c7
- transaction
- 71bc78e2c34a41a280a814ebbf44e469c4540cc7d644f5e1c5edd3c427f11bb0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26249
the chainentry 26249
- sealed to the entry before
- 5c202ec83dc1c1ca681f1413e52fb0bcf73f02df1306ac791efad20bf40c315b
- this leaf
- 72e3c991cbd86b4393e2660394471c4f8846a019e0206039b022f33060724536
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qlMAJ0ZCDW34aUOV1iEA9ISDm91lWsmSPCwQHRiW3SU/KKIDuPn5kAAAZe21P8EoveSlDD/nJyxvPi453XDnAw==