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
- 07d904b1276ab63f300c78903c9f57a7b12c3fb20cf6d65dbcb657d134bf078b
- request
- c9c07f5837c8947b56f14872b53547799709d5b3da764172cc1c6c7f35bd2051
- transaction
- 16f26eddbab72c802453a79e4ad725546d6bdb19e88a6089e2eee10609914ed1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30703
the chainentry 30703
- sealed to the entry before
- 340383718b3ef6e93494cd10d11694ac4b29fbd75767f1a8ce76539cbef6762e
- this leaf
- 0369f8bbee5ccae2d2b30748c507bfcc4ab6475214b636e0db437c9b3905c65f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- v4R3Pb7K3KUrTl+Xj0ym9Qbm5L8HShaRNvqbQXLLcV4O1E4pZ72ecTsQwsWeMbQcF30My+k/ZTO4KmpLeLs/DQ==