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
- c0193b906bc06410075deed3fd77e0ef3b3deacdb8113d4f160d1e71b36514f0
- request
- 63e907d4ee5ebacae96890a6b55b410b6941f53eb7757cbd5a85daba54d24832
- transaction
- 1574473b6979e6972b5c0e89ec83cef77ea2caf92f7b1d43af5ce83c097f96f7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32149
the chainentry 32149
- sealed to the entry before
- b47bc500c04bf2ffef75772db06a2f316d65cfe348f51ffcd1f86f58752d0969
- this leaf
- 6ade0072b6cecfc7ef0c1322b8c3c65514c363148343bcfd973ca2e44cc77d1f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5eTjCfgRaX1mk0ykO3Tw8sWTL25zeIh9sDdmx+/h7+qMwT/QX53dzcVhTR948ujl76WBOgnh8zvwWm1b35qLDQ==