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
- 6dd46e624c6f0c464754017f3d46f835c7235db64823187227e4b136629dccc9
- request
- 6bad3611f1c982658eac12607301bd33298c926ea26c7561de550b2cc36f96c0
- transaction
- 9c9e3fcbac2e52a1871332ba5404d7231ac7df00e0f96d1d1862fb12696d4d3bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29086
the chainentry 29086
- sealed to the entry before
- 6e540641998c88b012f4ee2b64c0f7af5877eba842d361afb4d62e5af718294b
- this leaf
- 4e965910097827e31a099d934ff60fa37ab8c9d134fd2af376b0338152ea5d17
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- j/GCvWgZISvUvDxR7iRBPLfPv/Dx7XBf3g1LcVlaWzyNkMoBr9R7HWGmqW/H9PbRGEUqmp/5WdTstpF9CRdDBQ==