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
- 12c9cce1f25a629b0353a18bfbc4879f6ec400d0f5202e780f97114b621bc420
- request
- 5574dad72bc913de8c17ad8bdd951188f8d08396de0e11178daa5438f4bc9651
- transaction
- ffd8b6810d398ea16c1bfe69545daa6f2b85bb1ed4392613fa7f6c47a53e676dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65634
the chainentry 65634
- sealed to the entry before
- ab36682e6de9d826bbb15b834ed885a93fac6b244a9cdbef3722a8f8ada158b1
- this leaf
- 80f278d83976ae5788326d53e4aa7c4478e0f13415de17554455501fecd9d20a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- agSKX2tMt7BkZmVD66jjvqwTA7un0NCU2yFx1YoCwiLsU/K87cnspwoVerqWpQiVk4Tu5cs9hEYRJW8qvGpSBg==