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
- 4ec71a5197c307a49441f0a607f6038f4e8b1ce30a75d62e23a844b88fad709e
- request
- 1dff30385794c9c29ffe9f76c9bff79dff2a8c0baa8d05abc1b502751a937402
- transaction
- 5c5b71ac99a0ea4b077907e5c9c6c4c5515fd2ad89df703b4fae0aeb0e333ce7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48360
the chainentry 48360
- sealed to the entry before
- 52ddb6835da1f9e50d07d72bed0bb75557b996e5dfb7f70b4f04f7e5a709881e
- this leaf
- 8bd0a10d74c2267321989397bd9c5d0b35e02375a230d402e98ef17732a6d586
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- divEmB/lxy2qgQa0x/gMcDJY+mHWcdj6WngMp0bUrAXPiTWzIm9W1XFoUxH+aJTtVWKd4uRL0Bdcz1tvwsiiAg==