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
- 2bd954e2134409fffd390f05f9a8dd2e936c65fd4713e7ddfb6bfcee2697e595
- request
- bd12dc77185d5e37034f6674e09292423b5914f5cfc8b37c9ee11aef90d92b82
- transaction
- 9bd25ce8bff9c1f7a61f713829e3e16b7d72abccbb228b177c2e538ec7c75df9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17311
the chainentry 17311
- sealed to the entry before
- 40a5def0aa9d7cb6e2641b01dc2768a827cfb2bc307f555f6f5fe37f51ed39ee
- this leaf
- d07e3fdeef7b21f700a6d9b8d730efd5b2cb55b0f4e4ce20892c5072aea05723
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BbzvBPNbVlgTZevdDN4eHX23WtEs36vSNYtsuqrSXm7/bXREDaxp3bD516/b2CmJ8n1ITm2iy4EYccXqQ6O7DA==