Incode submit label and resolved message in Blueprints

You can set optional features.submitLabel and features.resolvedMessage on Incode actions in Blueprints, so the verification step uses your submit button wording and your completion message instead of generic platform copy.

• Use submitLabel to name what customers tap to start verification (for example, "ID Verification") so the step matches your program language.
• Use resolvedMessage for the text customers see after a successful check (for example, "Your DL verified successfully at") so completion feels specific to your flow.
• Blueprint creation rejects blank configurationId, submitLabel, or resolvedMessage with a validation error, so you catch empty labels before customers reach the step.