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
- f8f1728734c57bfaf364de5294f65e7021d10aab26604c0ef4b0ae82e0123df2
- request
- bd8bf01e3252318721e2478b40baf2d3387b482c587bad41a80e80eb5f029333
- transaction
- bf0ca4c2ab462869b9f1ef5fa642fdc680b3bd0cf0e9eef7d689a20c29a53301computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6004
the chainentry 6004
- sealed to the entry before
- 1e91265aa57047822625be305a43bed7feaa771610439dab9a27bdfc243e172a
- this leaf
- c8643173cd131b6753186c207a20b8ed2d50c7f422501114c8510ba637198a3d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yDAJ2WHyXHm26DNR144EFZwvTK3Y4fytpFCCXRyEiOz9LaBknDfB/XslD5joXxfQInfGmQD3i99o0+R5LtWaAA==