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
- 8c018fd473608181b9a35681a54dab72ff56b27127b0ff0eb99336864b59bd00
- request
- ae71834eab0e81d3c5ef69d7641fee798e90539b40641d1d528077e9a59217bd
- transaction
- 704b84adcc56cb18fad92a9ce5ab323f630185fa6211b5eb730a6958acc39ad7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31293
the chainentry 31293
- sealed to the entry before
- 4e9d029a072805ca74c4c3e0f7357c8a901d23da74a668ed50c5a69c43defa68
- this leaf
- bfd992f79f4dd8f8e05ba4ef77d3c61c329e507d0adca67519f097d1ed1356ec
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 0I8l7iC2ZBsCbJiqIj77LQ35Qp3Ti527Q5U57R9cByLXEaOaNIFuuEiHjprG17iTT5TI+MQsTAZpxAIsustwAg==