Actions - Mojo Payments Knowledge Base

POST https://posgateway.paymentsmojo.com/Links/<Action>

Action	What it does
`AuthorizeXml`	A sale on the terminal: the PIN debit or credit question, tip, card read, CVV/ZIP prompts, authorization, the result on the terminal, and receipt details (last four, EMV).
`ManualAuthorizeXml`	A card number keyed on the terminal (mail or telephone order).
`Authorize`	Card not present: a stored profile or a CardSecure token. On production MIDs, card numbers are refused.
`VoidXml`	Voids a payment.
`RefundXml`	Voids what hasn’t settled yet and refunds what has.
`CaptureXml`	Captures an authorization, always for the authorized amount.
`InquireXml`	Looks a payment up by retref, or by order id.
`CreateProfileXml`	Saves the card on the terminal as a CardConnect profile.
`Signature`	Takes a signature on the terminal.
`Cancel`	Ends whatever is on the terminal.
`Test`, `Version`	`Hello World`, and the gateway’s version. No key needed (GET).

Despite their names, the …Xml actions accept and answer JSON too (Formats).

Partial approvals

If a card is approved for less than the amount (a prepaid card short of funds), the gateway voids the authorization and answers with an error saying so, and the terminal shows Declined. Take another payment for the full amount.

Long sales and recovery

A sale waits on the customer at the terminal. If the POS loses the answer (a network drop, or a sale left waiting for about four minutes), look it up with InquireXml by the sale’s order id before trying again: the payment may have gone through. Always send a unique orderId with each sale for this reason.