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
- 65db5334835c0c27e6bb0d2cf3d4a832fb5b7ef37e67492b19875ff49ca4d77f
- request
- 00af906e6d223194d649d33367bdfd34cec131ec0f39330dd941310734515e8f
- transaction
- 6a0640043848ce922df7e07c3bf15c14a7bf234ca52a6773c74f50f87057170bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46555
the chainentry 46555
- sealed to the entry before
- f27a49555306811189c34d44ef5c857cf1c989f0a6df2456c988121c22ec9d14
- this leaf
- ff37cb6e5208f1e2acb65bec81912d19554869bddd35063aa0e1ad87a4db7f14
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- N/E2giBl9NSF15F9FZpie7J7PhPbzjKKbINFTBC9LrpnBGKpJNq5e6t0YNYhBSFsJ2nUeQuPTnZ0FOLzxBE9Ag==