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
- fb3c6d075edd042955326ee6e70507488d689fa54ff1e92b5d81a8dac5e166e5
- request
- 46b646d654f4c5c0cb49a96da96fc24766e55a7ca99700b5a1a850ca8956f18d
- transaction
- ff3ede5cf87c1829b80685bfcd48538d43e5a0141272f5b9d73de3898555ec1bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14627
the chainentry 14627
- sealed to the entry before
- 94779749ef468aa5db2efb276be256b6bfc6e72699146c9348fa4a26dc9466b6
- this leaf
- 5bb8df6083f828d231c6d9c79774dee9c5bf25182d7bfd0c1c48e72907f8aa7a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EHwzZ5lztr+9C/SlJCTqWN6hQaa6skC15gvpNiLMxVxqF/ji43hRu+fQlokHLiQ9hmgZV98SSKiZG9Oiu4oSCw==