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
- 11d49c606738c5cfdada8f620e90050af55662984bfcbe867d26ecc602e2e121
- request
- f4dde2aa19faf86e1e97db50bce7d9c7520f21747c7d97217026d1658a403442
- transaction
- 3b05013bd33df04a732036d7f3f7d6d041baabd023c4197980345f8f752271b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 43565
the chainentry 43565
- sealed to the entry before
- 48c52584f9d0839e5ab46b5a94371e373c53cb1c60dd2c4e82097654d215352a
- this leaf
- 0c93b15ae587968291b5ab21ee08b75eb847c63c2fc2c52a422fe65ad729626f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SDqepfH47IUiNgKDZLy6EAiGDeoE8zUrtu+ExFwkPeD18V08JivL3NAi5HP0saIMsgwu9gw+mVKzO2LYb8kcDA==