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
- bfcab2f424f7018a72692695c5ac2e3f32afcb3b290c34a62e08b481369faf55
- request
- 3eb582ae459cf3cb213856c45ed08d104327cf70dfe513e6d1c49ff5ec58102b
- transaction
- d30b66a6e160c6310e03d3f663adaaebb62d3d3c34158dd246f314e5cab096aecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 10144
the chainentry 10144
- sealed to the entry before
- c831366b82c940f3b95dd4a0bef1237a2521c2abf05d193073a46474f0aecddf
- this leaf
- 71ac48fb45a3c993dfb45278e7f81fa193cc3f33a6519c0cf13ea5ba601fb959
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tM8fmS0/Cw9dwQEnK24dZoyw9y7liphCXaJqU3zZWOy+wER4fqq4Uqhvc3lnLVeV2mpxCZMDQMPLg3nwnWlEDA==