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
- e69f7eb036c9159f31998f977dcba43dc9248add3233184da46b2228850c6033
- request
- 895a2ff916f1545a2b49d1df4eb144fe573cf5018cf1a1294cbb895a9a860dc7
- transaction
- c1826ac62f293432c4fed86a669619670004eaa09a2d8805235143d5c71fc534computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57321
the chainentry 57321
- sealed to the entry before
- 4bd5346903c292149a77814f4fe1b9e4a276212bcda023f7ddb46309ee3a262b
- this leaf
- 3f8ea9f0b284ce193e1fb1ea1e3cd1b77b022ba512f4727159519833ca082c4e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +0wVcS+cH08H6m8/L5TKaVIjP2/AHd5TuQgMVDYhbrzparT2kQeXsbTFJdKYctNyIP9Z7jSXt7v89a2uCxvsAg==