ELANLINK
  1. Acquiring
ELANLINK
  • Guides
    • Welcome
    • Interface
  • API Reference
    • Introduction
    • Endpoints
    • Data Types
    • Signing
    • 3-D Secure Verification
    • Subscription
    • Errors
    • Webhooks
    • Items Information
    • Changelog
    • Acquiring
      • Create a direct payment
        POST
      • Create a redirect (iFrame) payment
        POST
      • Capture a transaction
        POST
      • Review a transaction
        POST
      • Cancel a transaction
        POST
      • Cancel a subscription
        POST
      • Query a transaction
        POST
      • Refund a transaction
        POST
      • Search a refund transaction
        POST
      • Create a payout
        POST
      • Optimise payment methods
        POST
      • Update an order
        POST
  • Appendix
    • Test Cards
    • Bank Code
    • Country Code
    • Currency Code
    • Payment Methods
  1. Acquiring

Optimise payment methods

POST
/v1/optimise
Our system leverages transaction data to recommend the optimal payment methods, aiming to enhance the overall payment acceptance rate.
By using this interface, the system will provide a list of available payment methods, sorted by the highest acceptance rate, enabling shoppers to complete their payments seamlessly.
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request POST 'https://test.your-api-server.com/v1/optimise' \
--form 'merchant_id="{{merchant_id}}"' \
--form 'account_id="{{account_id}}"' \
--form 'request_id="test123456796"' \
--form 'currency="EUR"' \
--form 'amount="1"' \
--form 'shopper_id="test03"' \
--form 'shopper_email="test@gmail.com"' \
--form 'shopper_country="JP"' \
--form 'encryption_data="2b0e1c1c5aedd349284f57c504b14fdce65853faef0123e1e0c4cbf5f931f379"'
Response Response Example
{}

Request

Header Params
Content-Type
string 
required
Example:
application/x-www-form-urlencoded
Body Params multipart/form-data
merchant_id
string 
required
Merchant Code or Merchant ID or Merchant Number
<= 7 characters
Example:
{{merchant_id}}
account_id
string 
required
Subaccount ID or Gateway Number
<= 10 characters
Example:
{{account_id}}
request_id
string 
required
Request a unique identification number
<= 50 characters
Example:
test123456796
currency
string 
required
Order Currency Code. Please refer to ISO 4217
<= 3 characters
Example:
EUR
amount
string 
required
Total order amount; value needs to be digits only. Please refer to ISO 4217 for decimal values of each currency
<= 15 characters
Example:
1
shopper_id
string 
required
The ID which is allocated or created by Merchant to specify the shopper
<= 64 characters
Example:
test03
shopper_email
string 
required
Shopper’s email address
<= 100 characters
Example:
test@gmail.com
shopper_ip
string 
optional
Shopper's IP address
<= 50 characters
Example:
111.111.111.111
shopper_country
string 
required
Shopper's IP country
<= 2 characters
Example:
JP
shopper_level
string 
optional
Shopper tiers defined by merchants
<= 50 characters
Example:
1
platform
string 
optional
Platform order was made through. Can be one of WEB, PHONE, DYNAMIC_PHONE, MOBILE, MOBILE_IN_STORE, IOS, ANDROID, WAP, STORE, MERCHANT_EMPLOYEE, MAIL_ORDER, AUTOMATIC_RENEWAL_OR_INSTALLMENT_PAYMENT, MERCHANT_INITIATED, UNKNOWN, POS, API_ONLY, PERSONAL_POS, PHONE_LINK
<= 50 characters
Example:
PHONE
encryption_data
string 
required
Digital signatures information
encryption_data=sha256(merchant_id + account_id + request_id + currency + amount + shopper_email + sign_key);
All encryption parameters need to remove spaces before encryption.
<= 64 characters
Example:
2b0e1c1c5aedd349284f57c504b14fdce65853faef0123e1e0c4cbf5f931f379

Responses

🟢200Success
application/json
Body
object {0}
Modified at 2025-04-21 07:36:01
Previous
Create a payout
Next
Update an order