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
- ab9eb35f5e1be9aa40feb5f270d4be502c64e026ae8c97b1787ac5107108245d
- request
- 762651f9db73f9d3e42d64623207a3a636623f384005cbb18158f22eeae01fb0
- transaction
- 8f1b6d330926813f194c1a10e055712427a2f00e380bde57bb1f197565ae5c35computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2030
the chainentry 2030
- sealed to the entry before
- 1d0f35313d0c4a3710ab6f8e846424d3da013aebfb2d7a86bc476d4c787b1d10
- this leaf
- f1014043bd788cff41af29e92ab21f83a421fef014bb5ad9677f1a2c64307ce8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- l922RqRWMR5IBvrZdyx6kHmT+foMREufFayr0T3UAD9rL2AM8whhorULRzCrv4exk/bOAq4ZxZFN71uDRw/DBw==