Authorize a paymentAsk AIpost https://api.staging.payrails.io/merchant/workflows/{workflowCode}/executions/{executionId}/authorizeRequest a payment authorization during a workflow execution.Path ParamsworkflowCodestringrequiredPath parameter to specify the workflow code.executionIduuidrequiredIdentifier of the resource in Payrails.Body ParamsamountobjectrequiredThe amount to authorize.amount objectmetaobjectMetadata for the context of an execution. Includes Payrails-defined structures for most common fields used in workflows, but can also be extended by merchant or provider-specific fields. For more information, visit our Meta Fields guide.meta objectreturnInfoobjectrequiredURLs from the merchant side where the consumer should be taken after a redirection flow. If no specific flow for cancel or error are needed, we will redirect to the value in the success URL. The 'pending' URL is used in case the consumer needs to be redirected back to a page if an execution stays in pending for some time.returnInfo objectpaymentCompositionarray of objectsrequiredSelected composition of payments methods and instruments to execute the action. We support one payment for each Workflow for now. Split payments and multiple payments in a Workflow will be supported very soon.paymentComposition*ADD objectHeadersx-idempotency-keyuuidrequiredIdempotency key to be used. Sending again the same key would return the same result without re-executing the update.Responses 202The payment authorization was requested. 400Bad Request. 401Unauthorized. 403Insufficient Scope. 404Not Found. 429Too Many Requests.Updated 11 months ago
