Skip to main content

Running an action

Quote each switch as a whole, as above. The CLI exits with code 0 once the result file is written, whatever the result: always read the file.

Actions

AuthorizeXml, ManualAuthorizeXml, VoidXml, RefundXml, CaptureXml, InquireXml, Signature, Test and Version. Each is the API action of the same name. Card-not-present payments (Authorize) go through the API directly.

Example: a sale

The result file

The answer, as XML with one element per line:
When the answer isn’t a result (a customer cancelling, or a failure), the file holds the message:
RespStat is A approved, C declined, E error (see Formats and Errors).

Lost answers

If a sale’s answer doesn’t come back (a network drop), the CLI looks the sale up by its OrderId and writes the approved result if it went through. Send a unique OrderId with every sale so this can work.

Interactive mode

Run mojo.exe with no -a= to type actions at a prompt, which is useful for testing. mojo --help lists the actions and mojo --version prints the version.