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
- 8567748f4f1dd876ce8b0e766b1e9fba470c20583b0577b55ed702f913b882d2
- request
- ef3edaca3680efba395fe506e5ad2f457b9638ce9e18d94589e9d2cd40c84a7e
- transaction
- 52435a48e66c6d2b2038bf1e40459344e4b78de7f75042457a855d90cd15cfbccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70183
the chainentry 70183
- sealed to the entry before
- 6db9a68089a777edd58dfce869a3bd1be9d1022853c511a89e85af312c3bbe92
- this leaf
- 5553ae94c75e2967d97b43f9f003248bdf8da45333f3a9f6eac7127280e7bbeb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6woNL3NCft6caqe8JXq93CJkKXCUMijc3X/jezj8Uvro9PDMULMCozf4yupalAq5fuG65icD7Cjs7tMIImJDBw==