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
- 1baee8eea1a0f24346bb0cbe8708fa8733f86442b69e6c12439035c7e212cf87
- request
- 66087ec325b18d05b62938ea419b46cabe54812c57cd969bf406b0ab8f9cfc5e
- transaction
- 275ab0cebe7487bd00663a394ecab2e87363f2a04bef6d99c8d5a43fc76881c9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 49784
the chainentry 49784
- sealed to the entry before
- f2a72a524de5500e4e4c879ac05152c880f9b492da15f1667f48da2516dcb71d
- this leaf
- e92832ee3ce58c1aa3c240fec72c813c416c909c9357fc13890271402517217e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /MGnmnlaMYjcfnwYCGF6sjObBOaRpAV+cHZT4M7WuGhHZfzlAU+IZd0CPWhwMfsGnRLaK8vdLyFdKqn9iR+NAA==