LPB

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant Interface Code
• Merchant Public Key Index
• Private Key
• Provider Public Key
• Google Pay MID (optional)
• Test Mode -> (enable if you are using sandbox credentials)

Choose Currency / Features; check with your Corefy account manager which are enabled for your account.

First request to Corefy API (MIN)

What it does: creates a payment-invoice; card data itself is collected and submitted separately by Corefy's checkout/SDK layer, not as part of this request. LPB uses an off-site 3D Secure challenge (redirect-based); after the customer completes it and returns, Corefy finalizes the payment automatically - this can take up to around 30 seconds while Corefy polls LPB for the final result. CVV is always required - non-CVV sales aren't supported.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

This connector also supports USD, GBP, PLN, CZK, TRY.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567"
      }
    }
  }
}

customer is entirely optional - everything is only used to enrich the sale.

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

No Constants are configured for this connector.

Options

• custom_finalization_logic -> optional, boolean - LPB reports a successful payment in two stages: authorized (funds reserved) and later deposited (funds actually settled). Enable this to have Corefy wait for LPB's "deposited" confirmation before reporting the payment as a final success, instead of finalizing it as soon as it's authorized. Also available for Apple Pay and Google Pay.
• set_additional_data -> optional, boolean - delays status checks (reconciliation) until LPB's own overnight settlement/clearing cycle has had time to complete, instead of checking immediately; recommended if you've seen premature or inconsistent statuses shortly after a sale.
• use_api_v3 -> optional, boolean - switches to a newer version of LPB's API; ask your account manager whether this applies to your account.

Refunds

LPB supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment).

Authorize / Capture / Void and Recurring

This connector also supports the standard Corefy Authorize->Capture/Void flow (hold funds first, then capture or release them separately) and saving a card as a token during a sale to charge it again later without resubmitting card data - ask your account manager if you need either set up for your integration.

Apple Pay / Google Pay

Both are supported for this account type. Google Pay requires the Google Pay MID field above; Apple Pay needs no extra LPB-specific fields.