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
- 58f8ee140bac867ee4cef44cdce234a04d2d402f1261dab80c891e91108926f5
- request
- 6db37e91da666730d734ba723bf65adc867acbab0e0fab4e62b085bce327e90e
- transaction
- 0f6c4550e74e768af02fd34960d05915e64e740077642ae9e3317a4f2e2b6b1acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2050
the chainentry 2050
- sealed to the entry before
- 94e5f3a4bc6fb4162255d15e7911f1bc19b30c3cdf9b10864de1b055f3623ed8
- this leaf
- 34e3eada79288f5635e34c0d75fb9dd8df3e0e5351fa64190c03d29fb6ba2c32
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- qTB/L4B/brPJEwL4SBKqQl4vuzoU2dR/HNKc+vyoOl14dQpjUOZuv9VDmzl54qoizOJ4emXrQ+yo0UvvW2sTAw==