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
- 0f95ac57ee0c21463457855fb802ab973a2c2db574e3fc971c5ff1cf3c0717e7
- request
- e5d594f7262d6c13e6fb85991c73e639d72b3d38f29e98133b88fd7ff5c6a785
- transaction
- 0d74fee80c391e30db2cc76f33516fed4b0d1135b986dacb2811862fb4db5490computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5552
the chainentry 5552
- sealed to the entry before
- c2f5acaba9cc385860d955c0446bed1b4601734c8eb10361195b0695ef926492
- this leaf
- f690f0842a46c1c9851e510e07721083cd9982848ffd191bad6df992a71ea10e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6o66z0bQfB+1wT2M/mMsY0I0qkJdPp1WKaCDgcXssG56gUuuInc5Ln16Rhz8j0TcWoPa4w1gVAAE4xYIPJ5BCQ==