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
- 3585522823e1932b7c490816d620e1dc4e18a157b5f666f4c47a58a5a6dc0974
- request
- d40af2ddfa952118b784d27baffbbf276eb4e189ce9dd7ea4f12f0daaaaccd6c
- transaction
- 4b815204d81d20446f1d3369efd6b7692c21517cb862b7452fb760153473243dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45381
the chainentry 45381
- sealed to the entry before
- 1357993b3cb4458a2faca5c76085b844e96b490e504613b92181c744ce10b876
- this leaf
- e6f62cec090e45783af3a3311f35883dfdd2983919d79d6cda018e7a5348c77a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- epv86jr5D0UK426vBfODFydsD0er3aWk6/llm+g0MhFHOdXHzONEeb2ebH52wuHccDNm3SLDHaEfhkBUL3IbAg==