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
- 8df7b508545b669e11cf253d9cf7b8368fb6fa48da828f75e95277e33a649f5b
- request
- e7c3efa83f90e48a8887c9acfba7e143339288042c07b54a7c0d8543f206bd4f
- transaction
- 093441c721ad541109b7cd00a91c2ba400a7585a84a367317ad2efa63119a76ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 301
the chainentry 301
- sealed to the entry before
- 8a779e198d14cb0703b015fd6d3c59e96352cd054876e61ad47b78fad51b28e2
- this leaf
- 677974251f282198b75767a15bad3c0fc726ebdea1b7f9c570e47d3a9e94ae89
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- S9mSRKGfa51W8wsoOwBHp3nQL63/1oItl5D0rhsMCScVcqXx+he+cP08UzWfozx+Ka3YrWV8Ui1DI7b/kcpbBA==