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
- 1d702be8fd7ef0a74441e8fa43047152c6549ed97bb6cdf6bbbc334b33afc5c4
- request
- 17ceb9336b75a7c6c475d73d756de7214b9a15ac428ae8ac0349cd85cb69f4fe
- transaction
- f78e9265e59cb21db85f81031fb6e84ff576f283b0154a82044134243f14ba38computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36895
the chainentry 36895
- sealed to the entry before
- 4988968f0b5d13a7ba540a84e24790fe1402b9bf0e41972cb8a316377a1c5b16
- this leaf
- 11bb126af2121014b625c844fbbb944270230aff8abe1a78f5fae72099a4af1c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7jQI2BYGGgCpmC6B+ZiKLk2QI4ZP603ktZkcXyg+NOthgBZEz+Kl/eESrkIfTD2Mta0mft8owRUCDYm+wQXeDw==