LemanPay

Advanced Payment Pre-Processing Solutions

Supports in this guide: Payments

Provider website: lemanpay.com

What you need to do for start processing transactions (brief summary)

Choose account type
Get your credentials (from LemanPay)
Connect in Dashboard
Send an API request

Choose account type

LemanPay can be connected in different ways (depending on your needs):

If you do card payments (H2H, card data sent directly) -> choose H2H Merchant account
If you do redirect payments (customer redirected to a hosted payment page) -> choose Provider account

If you are not sure which one to use, confirm with your Corefy account manager.

Prerequisites: get from LemanPay

Get the following values for your LemanPay project/account. The same three values are issued by LemanPay for both connection types below, but are entered separately when connecting each account type in the Dashboard.

API Key ID -> Corefy field api_key_id -> example: lp_key_9f2c1a -> where to find: LemanPay backoffice / issued by LemanPay manager
API Key -> Corefy field api_key -> example: sk_live_7d3f8b2a9c1e4560 -> where to find: LemanPay backoffice / issued by LemanPay manager
API URL -> Corefy field api_url -> example: https://api.lemanpay.com/ -> where to find: LemanPay backoffice / issued by LemanPay manager

Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open LemanPay in the provider directory and press Connect at LemanPay Provider Overview page in the New connection section. Choose H2H Merchant account.

Step 2 - Fill in fields and select settings

API Key ID
API Key
API URL

Choose Currency and Features. You can set these parameters according to available currencies and features for your LemanPay account, but it is necessary to check details of the connection with your Corefy account manager.

Success

You have connected LemanPay H2H Merchant account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_kzt_hpp",
      "currency": "KZT",
      "amount": 100
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "payment_card_kzt_hpp",
      "currency": "KZT",
      "amount": 100,
      "customer": {
        "reference_id": "55041b5b-adfd-4073-a92b-fd8b495a4cc1",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "date_of_birth": "1990-05-14",
        "individual_tax_id": "123456789012",
        "address": {
          "country": "KZ",
          "region": "Almaty Region",
          "city": "Almaty",
          "post_code": "050000",
          "full_address": "Abay Ave 10"
        }
      },
      "reference_id": "86e68af6-6b95-4cc0-be16-e4df8044604c"
    }
  }
}

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow

Constants (fallback fields)

Constants are static values that Corefy can send to the provider instead of dynamic data from your API request, when those fields are missing in the request.

Priority (predictable rule): 1. If a value is present in the request -> Corefy uses the request value 2. Else if the constant is set -> Corefy uses the constant 3. Else -> provider may reject the request or apply its defaults (depends on provider)

Currently available constants (constant -> Corefy API field)

FIRST_NAME -> customer.name
LAST_NAME -> customer.name
EMAIL -> customer.email
PHONE -> customer.phone
DATE_OF_BIRTH -> customer.date_of_birth
INDIVIDUAL_TAX_ID -> customer.individual_tax_id
COUNTRY -> customer.address.country
REGION -> customer.address.region
CITY -> customer.address.city
POST_CODE -> customer.address.post_code
FULL_ADDRESS -> customer.address.full_address

Payments processing (connect Provider account, create payment-invoice)

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

Open LemanPay in the provider directory and press Connect at LemanPay Provider Overview page in the New connection section. Choose Provider account.

Step 2 - Fill in fields and select settings

API Key ID
API Key
API URL

Choose Currency and Features. You can set these parameters according to available currencies and features for your LemanPay account, but it is necessary to check details of the connection with your Corefy account manager.

Success

You have connected LemanPay Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "polipayonline_nzd_hpp",
      "currency": "NZD",
      "amount": 100
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "service": "polipayonline_nzd_hpp",
      "currency": "NZD",
      "amount": 100,
      "customer": {
        "reference_id": "bc75bc54-5023-4f98-8c0d-ec5ed7e8f380",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "date_of_birth": "1990-05-14",
        "address": {
          "country": "NZ",
          "region": "Auckland",
          "city": "Auckland",
          "post_code": "1010",
          "full_address": "Queen Street 1"
        }
      },
      "reference_id": "08f5e97c-1170-4bda-9625-3bde3c6dcd20"
    }
  }
}

Extended request (MAX)

Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Positively influence conversion rate - Include optional fields required by your specific flow

Constants (fallback fields)

Constants are static values that Corefy can send to the provider instead of dynamic data from your API request, when those fields are missing in the request.

Priority (predictable rule): 1. If a value is present in the request -> Corefy uses the request value 2. Else if the constant is set -> Corefy uses the constant 3. Else -> provider may reject the request or apply its defaults (depends on provider)

Currently available constants (constant -> Corefy API field)

CUSTOMER_FIRST_NAME -> customer.name
CUSTOMER_LAST_NAME -> customer.name
CUSTOMER_EMAIL -> customer.email
CUSTOMER_PHONE -> customer.phone
CUSTOMER_DATE_OF_BIRTH -> customer.date_of_birth
CUSTOMER_COUNTRY -> customer.address.country
CUSTOMER_REGION -> customer.address.region
CUSTOMER_CITY -> customer.address.city
CUSTOMER_POST_CODE -> customer.address.post_code
CUSTOMER_FULL_ADDRESS -> customer.address.full_address
CUSTOMER_IP -> customer.metadata.ip

FAQ / Troubleshooting

Invalid credentials / auth error -> verify credentials for the selected environment and account type
Currency or service is not supported -> confirm allowed currencies/features in your LemanPay account and in Corefy
Missing customer data fields -> set constants (see "Constants") or provide fields in the API request
Not sure which account type to use? -> ask your Corefy account manager

Question

Still looking for help connecting your LemanPay account? Please contact our support team!