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
- b34fd01a00c7ea6c0eafaa9834201827b315cf972ea4ab14f51dc8961d9ca84c
- request
- c1c9c1faf084ea4ba60c3809ae7e3e7d7b131d36c0941c67221718a54c5db0cd
- transaction
- eb7150c97c3f02939ae795034a1dce5d96ae6d5fef70293a7cb38cffbecbd051computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1715
the chainentry 1715
- sealed to the entry before
- 7d66710e6f020a7782b64ad2c029c0065ff5104d6596135d10bdd231239cddf6
- this leaf
- 67c75858f5484c14d50f6656137906c2e9ee1b6c935dbe8b0d79b84ed200f3e9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0UB6/ZT+bQtF8lG+b2+3U687a4CwzCuZo3Yl5o4gBH59Kei55eol1CecNzooflJBnUF0YBa3/ikbaDeOE9lgAA==