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
- f070246ac476db76df863eb056cbae179f960b74141db1ba762157381fa678ce
- request
- 4c43fa31bf76c63d6e09bb4370128d1e1761f2c9cb6a771e23ea27f3d92c72e6
- transaction
- 47cd73a1549b2189eaf905f765c0743fe63605d62fbb9b3cf57328fe39e941fbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 927
the chainentry 927
- sealed to the entry before
- a6a66b1806d58be7cac74382072e85814bf06fd4a24a6c7edb384ff23385b60f
- this leaf
- 94d665c30438ac095be3389842d46d41f463db39a1de73b410235c12831e0832
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- reed92QklsMwaK7BdE+fHXDmgo92YKaNsc5ENW/2PU/9FjvRLZrsZHdeHsWk8NFQBO+dXTy5tfk067oTWD4TAA==