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
- 5a020fdf3fef72e6ab6c1f1101eb86d6b47f677e0d8b0a3c8d63eecf30ab6fb8
- request
- 6d960fc32872f101e83312206c834c46910248228c22933475ebe72d439b1b0e
- transaction
- 49984d64d1c85b7431d21a8ff94b8008b82fa3dbd5078207fb6cc4aa7293b8b0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54036
the chainentry 54036
- sealed to the entry before
- 3de910902ac944c398e5388518952b4d1c6471bc4eb16d8566e5f6119041f412
- this leaf
- 1c283694391d415e27dafc1a4399248ca4bee76195da498ad7dee84a90518a7d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mxya4jiAoorutkHXzG3W8kIpaLdliz3QvfOpHDdSaDojo8stFaalfAZKQpTguctqRMY1UDQLgoY3tW4MpnX9BQ==