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
- ac3f404c20230091b8e1fa7b9927a9c04798c2f273c714d3ef103d38896ebb05
- request
- 9874f77168be4b06d69a0625acaf2c0ed26118c55019891ef5e0f179cdc172f9
- transaction
- cc2a3018b670eb9b9df543f7d79bf324554fb58a3114f56b69cddb5d0236d529computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52964
the chainentry 52964
- sealed to the entry before
- 49fe309034d79a87ec2103b88bfa05856002d4dca49363f2101817efbdba48cb
- this leaf
- b760d510f0b2841f748b4a3b0725295b1fb71ceb63059c8fd7befebbcc827547
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Kdv024gRKoy8h7fXHgrz2CYcDr4Zhc1lRyjdKHDBJhD5gXCeEkZO5rymbIi75qbAehxH8EKzLHfvC6qLU34vAQ==