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
- 51dcd314041de5a99bae85987396ea604fa943cf0e9cc158e231205891f5fd32
- request
- 57a83eb14dfd29125bf0cb82dad628e009c81c847ada918468b56008a0c06b06
- transaction
- 2cfc3902146a540442f33835d3f7455c20f716be8fbbd0feed0b9420783ec7f1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42735
the chainentry 42735
- sealed to the entry before
- 39da03b71b66fb412f113a0b2ddb8a504e5c76fd44b83bb5e83abf57a60d96c4
- this leaf
- 044186be27085966248fd41a652f466ebef0242a66343120d683ba0ebff16d0a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- G5D0Gc+ckhDMNKWqooAnFOakS5vWUySdR3sl6bFb0TcpOKsmMlaREUvep9QL0wgCAu8pFlPFK+YL4xbnAIeSBQ==