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
- 54e9360a00790328682795de41c1a04b67719ad7cbe6cdb0a07ef8171698a3b6
- request
- 90b67c9d1d57a5089e724b3e7882d92e76a2d792c0936558cb75fce2fdb4bdf6
- transaction
- 7acba667dc3369afa084ec3b795e84b79b344fb895b113cc2c5b5fac8f5e347dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 39075
the chainentry 39075
- sealed to the entry before
- 8451a4133555ea3a6f5a65f601a7c68025cee113a6c094cfecef712ad9065d70
- this leaf
- caf4c1d2039a3cc0cc900adad196fa5259aaf45f31b8ea8645aeb6bc9cd64d4d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GorPtcU7pdMUv89DdTDs+prxASuiGzJewTKte0GDxcAJfz7NHTJ1GPR0dFsRoL1CGcDPeOlTgjbmMl5l57VXCA==