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
- 86a6d07d22c8dac38a08dd944fc6fea08d55d0285f8fbb9fb66445429e5333ec
- request
- 14677d9325ecbe16688dbeb9c9276b4013abc2d63133c72287c1937fe7ffde58
- transaction
- 97a58f1747ff157d871934dfcca4230007ee99539f4a61bbaef618ef1f07ee4dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23438
the chainentry 23438
- sealed to the entry before
- c8758b4d1e3df4b40f8705aed1cee4254ca90cece5c22148d59a1ad1ac22f85d
- this leaf
- 3ff20b8768082b3d3f85facebc1f601f61972df667fec30c8991241b85c045a4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0boYmHmmkkMXpKAbcesZxG2V3Fe/lSuAuYY2dx15j5Jzam5Dr+j5wjM1Zht3gwGBlrYNvnV6lv1nt/ldmJEhAA==