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
- 091f3d5a6e400c5ab67a2e6c8fce5b039cb095b6aec941109c2b81dba75a039d
- request
- 3f23e74753724b6ae591d8f94881ca4e865d43737aecb8f49f93d6fd907a1ad2
- transaction
- 1e3b5135bd7c66de30e94227d9eb94171d8f3522f24258bd7f4b11f79bda0c48computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60027
the chainentry 60027
- sealed to the entry before
- 39b57c4c7c7fe56f01fe632e298bf441c75c26cdba043815195598fab4c94364
- this leaf
- d5ffd5c82b3cdae2961969e94f3f502b99c53408ee691cba89b2a564133a8d92
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IUmCRZF9WVO/tEElVrUwR+AbRWzYqJftkgSSczzYedOuiELxHQagWu8ZgFk0ZOVtIqCmHj8VuYuEG6lshE2tDA==