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
- 221d63153ce6d6a359800955a8baaa3a9f6d4f6852b46f4a1828e7b14eba37b1
- request
- 81ec29d79b3dfbad7f9dee709e7388f8e9450515b2bf972ac068cf1dabc74779
- transaction
- 3a134569de551afacaed228934aa07069a1796ccc6b6a321691f113df78390b7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18860
the chainentry 18860
- sealed to the entry before
- bf7eb5cfcb6a55b133e45bb4f3acfea369aa99050df995ddf2b591da7ffdf212
- this leaf
- 81ec4bfb0850439365c4f5309fbe74c4ecbdff8692853198e64f7a982a035246
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LPE8U9uQ5a0XOlITSwC5PSnDQF0XVJe/yiEx5rJF3Hyz9jWYUy4uy3NW683aPW1mrkchsegm1+XX5lJTPt0+Cw==