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
- c9cd9a53235b54767dbc797e5bcb6dc54b95df14a60bebf8a3c6901f133a122e
- request
- 3b9047167d6cc5d9b34ed65f6eef02f5d854f7af1ad2f7c55b78b1fdab2e6a11
- transaction
- 054b484a51c8c0bfbef85fbddf7e342d3afcc5d339c86f81ad0b4ca635640a3ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71441
the chainentry 71441
- sealed to the entry before
- 472f11d9bc4b80d577de8516ae653af3fc9a90900b62f386e413c238fe49c6f0
- this leaf
- e5e4e41d20e9e5e7ca66af212c737a5e4722b52913ac4d8cae70a263be3ea61e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- uRS3Vf6KcV4bd9UylRRDENzVKa89VDeb08+e6rNcTK8siUcJcRaHPic8aa1MNYEy+rJw0pCvW/q2ejGdiIL+Ag==