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
- 0948d3d352e67a46e70c84af9cf1c171c24a7f017af4b44499db96069c4a8071
- request
- 4c681f87555ae5b064c5bf06df21b8efa84b9ebca641b85fe20c037c311a9222
- transaction
- 30ee59d904e7f673c9866b581714ff65bced877b4a3daf870611bab41804b40acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29112
the chainentry 29112
- sealed to the entry before
- 95ce0461c2608c5d200b9fe517c4fcb03e846c09aa4498881279ef204f1b5f33
- this leaf
- 8eaccdc7b2d5540c45a973806cd97974f0e63505b4080e7f448a0f7a00052d50
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4/f/NdUvoqoZgn24zgNzSzMaxnBwPZHBf6J/ietGNSp8GoF2TiqOQxXHOPBnvNuX3Iy6hIHj8VB0qEnSn4fcAQ==