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
- c01e581ffbf99e346822de81a81af0c197026821f7e8fd6347420f3b0d0e9869
- request
- 10718babd5547b8ecde9182a0ba094c5719be173eabc0591201c16d7c5ba9293
- transaction
- 101d269c9b7df68738ee6a89ea8668a0f8823fbd3407229654e69fae4c02309ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6147
the chainentry 6147
- sealed to the entry before
- 95c1846271ace5d0985a367f188f880e656d5752a08c83344d2c1b8555c800ce
- this leaf
- 15aefcd65101f625fa068846450a9f1ea04d3ce49616a050d9bb3cc8dbb5a988
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +tOjtCAJog5OH1Cb+s/hjJamtp7joTinKdlZc8maxyDgnna6y4gO4YT7KHawizPDwTXvrlH4CCFpCs6k4vuRAQ==