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
- b04fe7240e96d59a670173288f1c395332d1d20a55b6f42310534ab9cf3ba4f9
- request
- df971c5f2be37770cf923509bf150b674708067778b8d9331421ab9753075125
- transaction
- 305ca303478fdf08756a5b4f9246d0235b358b5e9f437e44292b23b2429bec62computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 958
the chainentry 958
- sealed to the entry before
- 550a870b8d999553c01f76c3ac513e99a9d749f3b2fa76931a9e436b888bbf74
- this leaf
- 516f1ce0297d9d83786e7fa551895d816af92c47d64a8da5533a70b69a12247d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1SOqADQT6r3D4YyTnYjq2k4hk4FBKnBC6yCzyVFQuyxKaZjl2AcolQz1drbYEM6hECqt8FMNQ0lFWTvaJpaHCQ==