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
- dc82b35cc2b4082ba64f63f109c51ae31c45a95b0bab8807e752ebc7753bdff2
- request
- 11c9599810c4f4d9f03af3bb7c07f7d1d63fb61978ac8a140b50fa4c89c12d01
- transaction
- ed4188d89ec67ff360d93134795fc3eae66f9a853186d184c4371a2f337d3292computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 54065
the chainentry 54065
- sealed to the entry before
- 5da108902e82afeafc94be5c1ff605ff3914c0fcb6a615a1ed4770443803affa
- this leaf
- 1aef489c65eec8e7602cb844f2f1520d65b5390f0eed2a6499511bf501174e45
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4ESJsO59OQ9p2tTilJSH+Ibp1i63rM+mIP4Ybr3Mbd4BXhg/DznnMyPJz3L8Zi4rCfF6GOPE7vMiCcFAYpXPAg==