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
- 74733a07a560193ee5a64aa1e11528bccab873bfcf8aaeba95be055403067c2d
- request
- d23127a9638993ed212d94a047e34dbcc44420d915c40234aaca97b1193832e2
- transaction
- 8b57e4076d621e5ed384abb2781532087b8f794133708541e24f45ac16eafddbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33120
the chainentry 33120
- sealed to the entry before
- 73732794274e38f3b27794e62da785f7f894226b83bd0d1821f71800a0553ca6
- this leaf
- 91fac0dd4cdc198f78f5b43ab1d0ac2e03f0fe3755537c0c10d726c1bcc82ee3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +6GjIN7X+FMZedo73jEYDdcAtTESGt3+VmlllKjWO3MGZqe5IdSIvit/zpu5nSw2GMGLnHpmqWzVNqFY73jrBQ==