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
- 8e1c38e6d3809f2394823eee4a32136db50e6e84de17b18cfe6fc7b453905c8c
- request
- e4e71f436308a94d30b857e27cee722f2a2b07799ecfeba2bdf01df706bbccd3
- transaction
- 5e348aa1d5e67bf2deb79833d958e15c2756470d4e0528676fc0bc7835cfd8a2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34592
the chainentry 34592
- sealed to the entry before
- 8afd2e2660f0a89590de986422ca61130d2ed287182ed9d2d914bcfcad1c945c
- this leaf
- 7ea121e5bcb8e195c97807d97f8c6e82bafbf784c5d6a13beee01616f8f97afa
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Hwk4Dk82WVJ/dDe4cOmJzW9LCFaBQ3qHCibW3JZ7PxSa4Ns8kGP995qUBn6BAAZ+OWqGV1yiLb9SaNjFuHJPDA==