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
- e28b48acd390a6d6957d625b5cac67ca032618cbb8cf36886db880c38abb5ad5
- request
- d57e8c3e3d694786df380761d35e6d6892c272847fceceaad09452ea63e5c1bf
- transaction
- 5f1912d229c86c4f8c5063ba423a0a2eb0cc23ae7d4054f6763adcec76c5d050computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73949
the chainentry 73949
- sealed to the entry before
- e874c002103c0eba4efd4b79d2a84399091b6af0a8782a43213a107a950293a4
- this leaf
- ff71118cf7843099200a4fe2aa67defe7c926bf26c452708826f82ea57aa12ae
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 990dYoieg3AutgV4WpB2O4izfmCsVke8KDyEQcy2TJ+SKCwW7sUPqIrl3/uZL0wyHEldJh9kWLJvZpgqCx0fBQ==