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
- 1f35b56bc0a26cdb1afb25a2bc18c012a6d03a6243856e4f5182655ffa41eb5f
- request
- 30f870f3719d4eaf1b5b6935d058e5b8b3e8dd8c1436b9dc1f109c317463564b
- transaction
- 36a205485e2c28f6439f1362278659c57208b65d2dd771cbc5bc8dd7e5e056f0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 44207
the chainentry 44207
- sealed to the entry before
- d2c18fbbce8a610f11d05b0af48928a8c495b632b6c22c989891a0e3da267abb
- this leaf
- 307dfd41e7d402f5481e5038c94e0bada9e885b74a998685c306c8ec6274690d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- //2NmU4Tb1MrqZQyDElW+cfvJhZ9+VI6je+2eQw21Ly6zOd9Bg64nWQkdka6FzndjHRdOKZ/A5duFayDH7i0AQ==