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
- 6e86d094702d02000fffa08045c5683a1054260b61e7926180c1efa4ca5350af
- request
- fae7ba6b5def19996515b335e395b14b9441be40bd01a875a1e2bf7454d6b852
- transaction
- 517751e418de8d48ace09eacde09674c842e462f2312c71ce8a576e6c31c670ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72353
the chainentry 72353
- sealed to the entry before
- 40c8ae67193c3974c59db5ff5993067c147023089f45cc8907728dc051525284
- this leaf
- aa4b4cccc2946f1d4e96ccf220fdf343b8310ad1ca5779c60850a24272e8b1f4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5VHUJGNl8Ic5hoTXSpp1wADwyw86KLJFqOkSGmYMFoeVIVUyvAGJfipqCGDhCL6kmQx/2t5O/1/0XbZkeYdxAQ==