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
- 1a02882a02ab0a5bb4dea6e29d1506383bfef8dbc46ad3ab2ca889edbf1a989b
- request
- 67ee12abc20dcf4d7736f33256a00179d699954b5803759f2929bac98bd6c077
- transaction
- e805f9d1628762082154f33620c303204e32b9587b0f79e43c6bfd9e2c505434computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 41832
the chainentry 41832
- sealed to the entry before
- 5905a142fbf491a2aa608f9693619a64e64656d7992de3aa3b795183606ff74b
- this leaf
- 2309c9d8cbf31aaf0759eacce263f7200c73171624f343e828f2121565a54b39
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /ZQB+KFOQdqRAe7FifdUEyb0sX3xnuqLGOYFDwc3Bdru2w4QbvDzkYNS6gC/3+BZUa50vArigdzLkOaEHMFXAQ==