Auth and capture together

note recommended approach is to separate authorization and capture as detailed here separate auth and capture https //docs sg latitudepay com/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" api /charge/create/{checkout token}/ { "bill total amount" 0, "bill currency" "string", "bill tax amount" 0, "is capture" true } 2\ capture the funds calling /charge/capture api is no longer required as the funds are already captured during charge creation recommended approach 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 https //docs sg latitudepay com/separate auth and capture