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
- af94d440ce66733770a447ec22716fcdb9ed9b9cfc0495b3d938dc95ab898a05
- request
- 9fc28f5ef715ea04407d11ae50e356de5a92f185f05a0835969da250f5a29984
- transaction
- acb129d39005c03c7c8acab4de303fbfc232f14583ad0090977851382dfca28fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 32287
the chainentry 32287
- sealed to the entry before
- 251aaa7d879e6b5b2e888837b97d37892e43e8f35fcc8cbcd3ec2a07d71dac29
- this leaf
- dd4ade327214528a3818fd697edad9d6c275919a48816087a173c283ab622cb0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3pxEqxKe0/Hk6yCKaQ5n/o4mROf8tDorTlVNWt+BXjiOlr++tlGrs5X4u38ckePx/OrOOk8oAhBIrMO4o4hiBw==