The lpmsInfo (Local Payment Methods Info) parameter allows you to accept a variety of payment methods through a single API. The lpmsInfo object contains the payment method details required to create payments.
With the lpmsInfo parameter, you can:
Throughout this guide, payment status is indicated by the following codes:
| Status | Meaning | Description |
|---|---|---|
S | Success | Payment completed successfully. This is a final status. |
F | Failed | Payment failed or was declined. This is a final status. |
R | Redirect | Redirect required—either a 3DS challenge page or a local payment method page. |
P | Pending | Payment is being processed. Poll the Order Query APIPayments API until you receive a final status. |
For detailed information on handling each status, see Payment Status Updates.
Combine lpmsInfo with productType to control which payment methods appear on the checkout page.
To display all enabled payment methods on the Onerway hosted page, set productType to ALL:
{
"productType": "ALL"
}
To display only a specific payment method, include the lpmsInfo parameter with the desired payment type:
{
"productType": "ALL",
"lpmsInfo": "{\"lpmsType\":\"Skrill\"}"
}
lpmsInfo value is a JSON string that must be escaped when passed as a string parameter. The unescaped format is:{ "lpmsType": "Skrill" }
To determine which payment methods to use for specific locales, see the payment methods guidePayments API.
The guide includes:
To enable additional payment methods, contact your Onerway account manager.
Some payment methods require your customer to take additional steps to complete the payment. The API response specifies the type of customer action through the actionType parameter.
| Action Type | Description | Customer Experience |
|---|---|---|
RedirectURL | Redirect to external page | Redirects to payment provider page |
QrCode | Display QR code | Scans QR code to complete payment |
ShowContext | Invoke wallet app | Launches mobile wallet (for example, WeChat Pay) |
The following diagram illustrates the customer action flow:
When actionType is ShowContext, use the codeForm and presentContext values from the response to invoke the appropriate wallet SDK on the customer's device.
Some payment methods immediately return payment status when a transaction is attempted (for example, card payments), while others have a delay (for example, Trustly).
For payment methods with immediate confirmation, you can verify successful payment (status S) through:
returnUrlPayment methods with delayed notification can't guarantee payment during the delay period. The status remains P (pending) until the payment succeeds or fails. During this time, many businesses hold orders in a pending state, waiting to fulfill the order until payment succeeds.
You can reuse certain payment methods (for example, cards or bank debits) for additional payments without collecting payment details again.
To reduce the chance of future declines and payment friction (such as required authentication, always set up reusable payment methods for future use. You can set up reusable payment methods:
Single-use payment methods (for example, some types of bank transfers) can't be attached to customers because they're consumed after a payment attempt.