Earlier action names - Mojo Payments Knowledge Base

The POS Gateway’s actions used to end in Xml, as they did on the Mojo Payments Windows service. They have shorter names now. The old names still work: a request to an old name is handled exactly as one to its new name, with the same request and the same answer. Nothing needs to change in an integration that uses them.

Earlier name	Use instead
`AuthorizeXml`	`Authorize`
`ManualAuthorizeXml`	`ManualAuthorize`
`VoidXml`	`Void`
`RefundXml`	`Refund`
`CaptureXml`	`Capture`
`InquireXml`	`Inquire`
`CreateProfileXml`	`CreateProfile`

Signature, Cancel, Level3, Test and Version keep their names.

Authorize changed meaning

On the Windows service, Authorize was the sale without the terminal, from a saved profile or a CardSecure token. That sale is now AuthorizeToken, and Authorize is the sale on the terminal (what AuthorizeXml was).

If your POS sends AuthorizeXml for terminal sales, nothing changes.
If your POS sent Authorize for sales from a token or saved card, send AuthorizeToken. A token sale sent to Authorize is refused (it has no terminal to read a card from), so no payment is taken by mistake.

In reports

Payments made through an earlier name appear under the new name in the portal’s POS Gateway list. Payments made before the change keep the names they were made under.

The Mojo Payments CLI

The CLI keeps the earlier names (mojo.exe "-a=AuthorizeXml" …), so POS systems that ran rCharge work unchanged. Each calls the action shown above (CLI commands).