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
- 8a430ef141365ebc9db5c5bc9db0a166ccdd50a17a7e3d9b97e3d0c46f7087df
- request
- ac68884034d8f231e9a85624e3fa9e5b64a434851a6f046297f8a8294bd1a1ac
- transaction
- 8213a5fbb427e3a3daba6b02cfc683a5a283d3100b66c1bacd4b763f648a10a6computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50594
the chainentry 50594
- sealed to the entry before
- 7aa1cb7c0a3db3ff12e78901cc4254cedfd98cbd34b5327cd2488f14e95042a7
- this leaf
- 52eecafa780729861ab4d9bcc676af7f767d4202c3a3845a9d4c7bcf05f654e8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7p2S8ptuia+TfVi0jqet+bOy3sUNiigDutcnXulToL70rnh//T26hlq8gjiXY+MDNjD31m4Xb6e6hDlAgFDtDA==