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
- 1dc59758526b65c6a63d80719762ca19a4116c182b54f7410f2c9657a291d8e2
- request
- f064dab395ff210d7841a83e77f36478031ae82227446d97d72fdaedf219329c
- transaction
- 1712e9d78ec8a6390d024edea89e9d511ba2b1a1e5bf69d9ede34e7772c2b2b0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48674
the chainentry 48674
- sealed to the entry before
- 12c56af82650f1e4a4df6265e5fe21091590cc5e28f972f6656bbad8e2c4f523
- this leaf
- 7a3375e89c45853c33c7f6b7228626b09fc9aad04658de20261e9d8343ec6d9c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QIwfnNd2EnyCtuD+Rnd3kUUm71B/ziYoNpT/rg6HZGtu58pox4Ow6N4Auk+DNX/g8qpOH9CoBFiXL4fwxA1ADQ==