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
- 1dfb8eecebff1dd40c3fdcea00d377facc0a68fd4e2c323f2165d95950114773
- request
- df2d97aac6d87fe990df75491450fe8f6edc669c51d40184b5bd2b99b29849c0
- transaction
- 38c679156c642142413093597c5c70f537a1416b42f8d77bdbed7d0755471533computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46083
the chainentry 46083
- sealed to the entry before
- 3958eb2359d44e9222fddb64e60f51ecdbb0c84aa9c7b599adcdc3aa79d5ca8f
- this leaf
- 8e4593702fc7266f00aa4335a7ba6f7da803b859395093a5b30cd7d4ae663427
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- q5KMOrIQeYshnopVYZ1LCM5DYuZVQ7b5ciK7NlsZSONQX2vFp984yZsvcXcvreFbBT/WCyc9ffoP/CctIWodDg==