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
- 5abb7dd8436589322c4719e508757769dd856a244be31ca348ec19aefa4fabed
- request
- 5c96f034ca6468d1fb0e74debe4b3b2b9e2217230a1fdb0f09dcba9d6599805f
- transaction
- 9145ab56a236e95a5ac6ca60679830b0257d72324eef02d63970eedab486b3f7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39219
the chainentry 39219
- sealed to the entry before
- ffaacda84e13038c52d1edce53270f07a0faa1a83cb992b2a75a8919c17eabc6
- this leaf
- 712c4b798b60c026b6660531e0cee19bad838bd1253dc0436ab73218c1c8253e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HBEqmOJ1Cx0EWWDsx18gjVoDbtniGaN3ljAdcLUpv/WvInng/0ZxHMrH5T+zD2cV75O+9v178c3KYUsZb8otAg==