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
- fc751fd6147fe1027c979e426cd05a4b2f5e215118e39d1cce30acb847eba807
- request
- d87bd8ad3341b1d30936e76b88800308e194dacf7138690e5199f031eeafe969
- transaction
- 7daf7f42dad6393abd4650dbd3e3ee5cc48558ecf0a71d6f7ba2674071a8ddf2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40344
the chainentry 40344
- sealed to the entry before
- 7d17485d7d11a5f7b0c3a252da5013de00be4d3572593c7293e7caec91d7e344
- this leaf
- e3559313065ff710b0973d1468ee7f83ec106b80a0956999d2cf04c92a4fde05
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OYt6+kqXGn1aaJHnBGG/0XnpLRU7n/np191hCPs+PYjEeTp78JBv5DDkXh5Xsiv1YKRli7sxC6agVjt5JJvWCg==