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
- 7352fd0de02015e0eec00879e5d039469bff78d949047be003d2b5ba129bc37a
- request
- 68269f7f0a4098d12e63287778171f64c7c97a17412c24ea448988665960f561
- transaction
- 6c4cfd8c0404a845af40b189c9ef7a21bb9dee63986969dfc7a943672e5bd460computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70456
the chainentry 70456
- sealed to the entry before
- c7cb7f113c87e4e9008d471af291f456cfca17ec41ba2f20b4f8f2031cfc1090
- this leaf
- be3851032f32f069db7e172a57be27defb58c0780a27d4fa6de15f0bd1c8ca54
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fxjCl7e5za/5jGSsNo+alT7hSAup5EBk6oqxmfWp4EKGoOMII3UZnZiotxcipZBOsstqL6Jnzwd0kPWBbn5BBQ==