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
- db5a94f75796c31a34f25f0e2894ebddecda3172c5858588fa074504f413cc2c
- request
- 7c537af51f6e424fb1ca029f51bc606aaea426a7b75e09d719ab0dc3ac507682
- transaction
- 53a9799148555a03a59f0c04e97d8daddc4bdde47cab6c375dfffbf08a0094f7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 57616
the chainentry 57616
- sealed to the entry before
- 0fca9fc0a97422c0212b95d46e80666f484f87de33a451a964f4213b766df9f0
- this leaf
- 4f0e4ae3d9503ebde75ea798de6d9a40c33802d785ffdf15cd593bbcaf316042
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EL2sJ9ZJk1d5ri0wnTRCu7k7TL5OQhqGBcZmgpr7tA3YQ/gouWeZDdgtUxyTxNQ5y9XGXZz76b9IzBUenavKDA==