Skip to content

Logo

ConceptPay

Supports in this guide: Payments, Payouts

Provider website: conceptpay.org

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

  1. Choose account type
  2. Get your credentials (from ConceptPay)
  3. Connect in Dashboard
  4. Send an API request

Choose account type

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

  • If you do direct card payments (H2H, no redirect) -> choose H2H Merchant account
  • If you do redirect card payments, or card/SEPA payouts -> choose Provider account

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

Prerequisites: get from ConceptPay

Contact your ConceptPay account manager to get your account verified and receive the following credentials.

  • Merchant ID -> Corefy field merchant_id -> H2H Merchant account only.
  • Secret key -> Corefy field secret_key -> H2H Merchant account only.
  • API key -> Corefy field api_key -> Provider account only.
  • Secret key -> Corefy field secret_key -> Provider account only.
Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Merchant ID
  • Secret key
  • Currency / Features -> choose values available for your account
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected ConceptPay H2H Merchant 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.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6be05631-8710-4b14-a369-1928a2b70eda",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "name@example.com"
      }
    }
  }
}

Important

customer.email is required - ConceptPay rejects a request that doesn't have one.

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "199be985-c243-478a-86a8-4b8c902e5bb6",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "name@example.com"
      }
    }
  }
}

Important

On this flow, only customer.reference_id and customer.email are used - no other customer fields are sent to ConceptPay.

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 ConceptPay 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)

  • LAST_NAME -> customer.name (last part)

Refunds

ConceptPay does not support refunds on this flow.

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • API key
  • Secret key
  • Test Mode -> (enable if you are using sandbox credentials)

Success

You have connected ConceptPay Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to ConceptPay's hosted payment page.

Payment - MIN

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8afec793-9b41-4dc4-b281-c76cc54ffb89",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "name@example.com"
      }
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "06fa1ea9-8a5b-4dbc-b67b-6236b3b9af3d",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "name@example.com",
        "phone": "+12025550123",
        "date_of_birth": "1990-01-01",
        "individual_tax_id": "12312321",
        "address": {
          "full_address": "1 Main street",
          "country": "US",
          "region": "NY",
          "city": "New York",
          "street": "1 Main street",
          "post_code": "10001"
        }
      }
    }
  }
}

Important

customer.reference_id and customer.email are required on this flow.

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 ConceptPay 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)

  • LANGUAGE -> sent as the checkout page language, independent of customer
  • FIRST_NAME -> customer.name (first part)
  • LAST_NAME -> customer.name (last part)
  • DATE_OF_BIRTH -> customer.date_of_birth
  • EMAIL -> customer.email
  • PHONE -> customer.phone
  • ADDRESS -> customer.address.full_address
  • TAX_ID -> customer.individual_tax_id
  • POST_CODE -> customer.address.post_code
  • STATE -> customer.address.region
  • STREET -> customer.address.street
  • CITY -> customer.address.city
  • COUNTRY -> customer.address.country

Refunds

ConceptPay does not support refunds on this flow.

Payouts processing (connect Provider account, create payout-invoice)

Connect Provider account in Corefy Dashboard

Uses the same Provider account connected above - no separate connection step.

First request to Corefy API (MIN)

What it does: creates a payout-invoice for a card or SEPA transfer payout.

Payout - MIN

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "efbf0a2b-5590-42b7-b10b-94d49452147d",
      "service": "payment_card_usd",
      "currency": "USD",
      "amount": 150,
      "customer": {
        "reference_id": "cus_123",
        "email": "name@example.com"
      },
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Important

  • For card payouts, customer.email is used (falls back to the CUSTOMER_EMAIL Constant if not sent); the cardholder name is taken from the card's own embossed name.
  • Every payout service requires a METHOD Constant to be set on the connection - ConceptPay rejects a payout if it isn't configured, regardless of what's in the request.
  • SEPA transfer payouts require their own set of recipient fields (IBAN and beneficiary details) instead of fields.card_number.

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)

Currently available constants (constant -> Corefy API field)

  • METHOD -> no API field - required per-service setting that tells ConceptPay how to route the payout
  • CUSTOMER_EMAIL -> customer.email (card payouts only)

Refunds

ConceptPay does not support refunds on Payouts.

Additional info

  1. Active reconciliation is available on all flows - Corefy can poll ConceptPay's status endpoints in addition to receiving its callbacks.
  2. No recurring - this connector does not support saving/charging a token through Corefy.
  3. The H2H Merchant account and the Provider account are two independent connections - the credentials, Constants, and currencies available differ between them.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the credentials for the account type you connected, and the selected environment (Test Mode on/off)
  • Payment rejected for missing email -> customer.email is required on every Payments flow
  • Payout rejected / stuck -> confirm the METHOD Constant is set for the payout service you're using
  • Currency or service is not supported -> confirm allowed currencies/features in your ConceptPay account and in Corefy
  • Refund fails -> ConceptPay does not support refunds through Corefy on any flow
  • Not sure which account type to use? -> ask your Corefy account manager

Question

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