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
- e30eae8fe7f1ddbcd9bbe5077537322fc18c74c653319b9c8983d5019e1e688f
- request
- 0abfa98140b20461bb0d1cbb73209ccde24711325f8a785d6bc996671465ea3c
- transaction
- b4004e7c5b8b947257e352cf5feaff2e2ff7357e01892799f29c20657cc834cacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1410
the chainentry 1410
- sealed to the entry before
- c24708c42005c5f205c9652737a0e167db50c6376861339879444517f8750d05
- this leaf
- 68c593f435eebaa1af95225adadd8fe7cbcf9bcacd7ca289bdf880d27e7d7746
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- L6bvHuckDd5VNGPojZbJjoqbHWVjOpMzrzAWEc4Tymw6D7i9AyEuAWxVLvQAINpNCSlL4myvmU+35rV3/gr8CA==