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
- ce20dd2bf778529532e7b5779c0388d4a8d0f88795af30d1e2843182fb3bccab
- request
- f89071dcd33410c4aabe9aa0bac875027c5d5ce3f3e146738e012641a8c7def7
- transaction
- 429d320fd1313ad3ee76bc9996de563971222ff09174afc4270aebe532d91e8fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23558
the chainentry 23558
- sealed to the entry before
- db66e725561c1915afa443b560b9231b17cd9a48f1b5201fc056a4bad4c8cb21
- this leaf
- e78175d67005e14c1b3046619174c0eeb17b411408c3f5c246b84c61c07eeeed
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mvV+4G6U2vrSJnvykyik/2yCYEU3GV5rNy1jldByyzPjQm3TwX/i2zz39l6m/Z7B9i1/KBs0lL1Gy3micMJKCA==