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
- ce27ab6bdc08fce217c4334881f2e6915bbf35eaa4c0bce3004625a8c2820f28
- request
- d12af636d1828f75aadd5c820f039b8b63b139579b8960a02cd4714ac297bd13
- transaction
- 45690f850f0251231da96fd1a99c38dd5f9f15fa8227acc07e163523da9f712fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4847
the chainentry 4847
- sealed to the entry before
- ada9e6b8ba3d0a7047007f4e4975832f77b1d19328b6a261a1c9c444e6679b96
- this leaf
- 987979cf36c0a91e7dba1b4e16cf9d7c6d75bdb10f2792423194470c8d2ab205
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Wd4Yclktph3/c1PNoL4nBXa1CQ14PEuHhLUGfYFsP3SP/kfRm1rIKNf6LN8WqqN86O1aQj+h9W98tMNgIMI4Ag==