If you are a user of LMS and Secure Payments, it is generally preferable to submit new payments to LMS instead of Secure Payments. The reason for this is that transactions submitted through LMS will be processed and recorded in Secure Payments, while those submitted to secure payments will not be added to LMS.
To submit a payment through the LMS API, see the Add New Payment endpoint.
When adding new payment transactions to Secure Payments through the API, there will be some variance based on the processor used. However, each call will use an endpoint and payload that have many similarities.
The endpoint structure is this:
The Processor_Type will be replaced with the appropriate option from the list below:
The Processor_ID will be replaced with the ID of a processor. To create a processor, see the endpoints in the Processors section. Make sure the ID you use corresponds to a processor with the same Process_Type provided in the URL. To pull a list of your processors, see the Get Processors endpoint.
The payload for each call will include 3 objects: transaction, payment method, and metadata. The payload will look something like this:
The transaction object will always contain the payment amount, but it may also contain other things (e.g. the direction of funds) depending on the processor and the functionality they offer.
The payment method object will be named card, checking-account, or savings-account, depending on the payment method. It will always contain the token for the payment profile that will be used to process the payment. This is the token returned by Secure Payments when the payment profile is created.
The metadata object is typically empty but can contain properties. Even if it's left empty, this object is required for the call.
For more information about each processor and how to run transactions, see their respective pages on this site or our general help site: Secure Payments API – Payment Processors