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
- 020ccb93ea9d610c4338fe3fbcf48064e162822adb842398663732f7e104c621
- request
- 678c3346cba885f32ff888de2eb7a083a90807a6967c429613d1ca890fbc734a
- transaction
- bc7f741e600083c0e2c856e0c63eeceb6116faffc802b77643d53ef587307d48computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31348
the chainentry 31348
- sealed to the entry before
- 57d600c525f429603c207739d25d45a58726ad55a6da784b360d544e4c830c03
- this leaf
- 3371f6ab490347745b9c811dffbd8006fb64a6b316394aa7a236fa0be2de5430
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- y0dMvVk7EVZgApiequjbNbFKC6OZ6ht9Zr+rUFd6rgiF1VmMxHxfIiAi47ofYY01MnCYXbZUgheWAUlYcHRECw==