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
- b0ce6372590c2a053015974d6af19d7635b5b5b879ad9b9404d1fb14ae5de25d
- request
- 3d6c0c14075e6e88fb07d921c4f2671d4fb109698721f494423f408096fc39fa
- transaction
- 0e114dbe2ca108063ce86411ab1d279f3ae6692ad89203e903f5fb808574c8ddcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58392
the chainentry 58392
- sealed to the entry before
- 12840e1306c6911d5a1a3abbdc4845a082070649d94d76de61db7e2013a4f3d7
- this leaf
- 70d4baa6e265271e36c0a15bcc7e04bd850983cf9a8fa56357c16db8682a403b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GortzgqTNtts9BTSntsAv85DyiYue5pM82AgpIarstetD/W4h0eeuDiPSZ1rgOX/Rb5/tkCQnyHBKcx32uy5Ag==