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
- 2eba58be811759c4b791ccb78d4be631f9f1048c948ebbad96cdf1e4ceda5a71
- request
- f05bd849e8cb79534e244dda02c1d617571c6930b82a1e272a4421889134750d
- transaction
- d72107628743db3f96a899f867bee9f24fd317e27b0ea2d4d631887ef1e6f32acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 31
the chainentry 31
- sealed to the entry before
- 35d69ed63e062af19290122288dcc86ce103b52e816b4825ae5e16f1b0d50011
- this leaf
- 081de40cb1a3568d89ee49a03990b8b25fd0faef0707974de5823c2ef40446ae
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3P2T8A0Pv5fL/+o8T5wW4XdOJlEpzFJJOXShmfgV0Xnjl4vzHnW1UzdnvO4XzcWslPGym7c2HwYpq5qq0IijBA==