Lqpay

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• App ID
• Merchant number
• Secret key
• Base URL (optional)

First request to Corefy API (MIN)

What it does: creates a payment-invoice; the customer is redirected to Lqpay's hosted page to complete payment via bKash or Nagad. Four services are available on this same connection: bkash_limited_bdt_hpp, nagad_wallet_bdt_hpp, bkash_p2p_bdt_hpp, nagad_wallet_p2p_bdt_hpp.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "1f2aa3ca-abd8-4741-980d-4017ed30cb8c",
      "service": "bkash_limited_bdt_hpp",
      "currency": "BDT",
      "amount": 300
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "2a3bb4db-bce9-4852-a91e-5128fe41dc9d",
      "service": "bkash_limited_bdt_hpp",
      "currency": "BDT",
      "amount": 300,
      "description": "Order #123",
      "customer": {
        "reference_id": "ce211746-9b3a-4b82-a760-ebd0808572f9"
      }
    }
  }
}

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 -> Lqpay parameter)

• SUBJECT -> subject (falls back to your own description field if not set)
• DESCRIPTION -> body (falls back to your own description field if not set)

Refunds

Lqpay does not support refunds through Corefy - there is no refund API call for this connector. Lqpay's own transaction status does include a "refunded" state, so if Lqpay refunds a payment on their own side, Corefy will reflect that status change, but Corefy cannot initiate a refund.

Connect Provider account in Corefy Dashboard

This uses the same Provider account connected above - no separate connection is needed for Payouts.

First request to Corefy API (MIN)

What it does: creates a payout-invoice and sends funds to a bKash or Nagad wallet. Two services are available: bkash_limited_bdt, nagad_wallet_bdt.

Payout - MIN

POST /api/payout-invoices

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3b4cc5ec-cdfa-4963-ba2f-6239af52edae",
      "service": "bkash_limited_bdt",
      "currency": "BDT",
      "amount": 300,
      "fields": {
        "account_number": "01712345678"
      }
    }
  }
}

Payout - MAX

There is no MAX variant - the request above already includes every field Lqpay's payout API accepts. customer is not used, and no Options or Constants are configured for payouts.

Refunds

Lqpay does not support refunds for payouts.