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
- da31e87830283545049bb3251cc41306b0106d0933bba7e82fab29f7ffcbfa24
- request
- b1b92309d7d070ea2ff8e71208fe06c0a40bad5893e900a303c0ddbe28c3aae6
- transaction
- 0c91280a9ef24aaa7ace619a932ecd07e62f21fd01be4552a5c09085e54ff8c9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40172
the chainentry 40172
- sealed to the entry before
- 1ddbc5d9d911343dbf6dff56d419a96c8a2da839795b45417ee7d1ae02861ba8
- this leaf
- a66675814c54e1b801c160cf54c72ff379e79df8d209284d74dad096851eb37a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nN5c6Q3rU4AsMxQdvN/GsIpeM5Af/VBajKX4zWWhPanElSoPiqAe1KoY7iFajTUpxQqcY3lGlS8uX8W0e/lwAg==