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
- 1cc96e8f2e8f33a2e91c6d58539b9ad0cfc20dd4faebf643eddb98e2f101ede0
- request
- 4801763ac490099cb0d0d2933abce07620561acf57eaef4bf78e7ca7cfb0e787
- transaction
- d23688afcf8ac39b3c3342133c7c59b2db77864264760136e75edf934500e319computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20154
the chainentry 20154
- sealed to the entry before
- 36496476d3cc7d093aec9691009d93f7891bd3c25ffa005698a2235a9348012e
- this leaf
- 6df1978c03294ea8f98bea65a5cd2fb74eff842dffac661051dad169cfdc1e7f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- s+Gu7qetRiuIYA6HEQOI9Iu4KBLM/oKaITAorM4NYfuRqlcoVV3rNANb7cjhIED+PagHI058GxNsk8Rs9CsNCA==