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
- baa9a032eed207bcaf500665b870111864e565210de03bd62480a9883c76e04d
- request
- a49cbd2c0c9ee9e2c40f31df2b8de59e5e1e7c35114e1b97d3ba713e3eb561ef
- transaction
- 166612acb164f883c090de566e78488b308ea026096a675e89693b7c60f8584ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50973
the chainentry 50973
- sealed to the entry before
- 80d8bdb90ca732ef227faade83a5ee61df6b75266ec761a693f7dc0a53cf3902
- this leaf
- 9c0802cf305ec908797ef4e3354b7e573f586bd1b41d740c5bb35000042896a7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- rH3EyfYzdQhgJckBnB2hTbsT5tEsKGOth+nYUHYbPPPyAHnGaE1M7nzGMp9Wfznw0f+guQJ/3b51JK0PRB0PDA==