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
- 801bc419ebc16a0ab82eced34521770e1f043b47ad41542f8e07f0c0a892b823
- request
- bb8bdb40216ea384e7e52836c8d05eb2b0781632a8411eb3a808f7bc111ec19b
- transaction
- 444a6f9584da00e93bb3814fe1c28a5ca827b259f5b43ba6445e1962fd2b5678computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29003
the chainentry 29003
- sealed to the entry before
- 48008fddafde39b74c26d97ebe15a42e749502a1ce46dd17388a8268cb361f0b
- this leaf
- 249976098e4b36113b31ca16c98fff1a221eeef64f696084ed8e12078c077370
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 9CL14tCE4EPW1I3a9BJHDpyEU2MhdPCuVbw4BMNS3jOALo1D1FneaDQzeIB3imnWHGzCzg9g+UFEpVxIfZAeAw==