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
- c9e59d41698cf1107b7363929834be9cff0a58b75fff4d57ce586981c008c89b
- request
- f29196684d4613fc1fb2868607d5a985929a18b6cb2d71faf9e732b997a1d6ed
- transaction
- a38785d701d3ce945f9f0425ff2f5d6d6122da51fea8b3a69ffea848f5a812e0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43988
the chainentry 43988
- sealed to the entry before
- 8c40096bd388fdc5b0dd257738e5c739925d31f9af2ccf2e327080d34c15c458
- this leaf
- 7c2bc5c98e0d3c3f51c4f7e3bd71ce62da3a63df73dbeec69dd6baa15d0f2c2e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NLw0t6UXptWPdQ5rqoCfxTGQwELVdXyhssXAj1vhA2rCezif5nWekiAxsXng+/lYiYaubB/MB5yFBFUwSgMLAA==