Auth and capture together
Note: Recommended approach is to separate authorization and capture as detailed here: separate-auth-and-capture. Don't be lazy! follow the recommended approach of separate auth and capture.
However, just-in-case, some scenarios might require to place a hold on card (authorise) and capture funds at the same time. you can do so in the /charge/create api by passing is_capture="true"
Calling /charge/capture api is no longer required as the funds are already captured during charge creation.
Use separate auth and capture as cancellation of charge if your customer cancels your order does not levy you any fee!
See: Separate Auth And Capture: separate-auth-and-capture