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
- 280b2308bd0ca07bc18bfbd46b14f2f843a5b7623750ddf4663f852f6febbccd
- request
- 37d88f916abb6a01869ed8ddb03ee2a415ad6cdbd3c4ae20e6b95eb4ea69d65e
- transaction
- a4ca0df1a5caf86dde5a1a25c29c8bc2ac16f1361a54d57772ee8309205e8c4ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22104
the chainentry 22104
- sealed to the entry before
- 0c2951853d680da56bcc27f58e543a804be49b3bd3c7a99a2e32a7d6edf33bfd
- this leaf
- 10d1ba29ee59d4016fea78a5c429f7f077df640041abf4597297db0e88be29b5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pKUMseOESQBzD7ltgSIquXhEpBYEbuN2x5Y8Wv2pxVRN4JzZmT/tp3ajxM20ySXPtzziAG1vultV6Muf986gBw==