Skip to content

Logo

Unicorn Group

Accept Payments For Your Online Business

Supports in this guide: Payments

Provider website: ugpayments.ch

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

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

Choose account type

Unicorn Group can be connected in one way:

  • If you do card payments -> choose H2H Merchant account

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

Prerequisites: get from Unicorn Group

Get the following values for your Unicorn Group account:

  • Merchant ID (MID) -> Corefy field mid -> where to find: issued by your Unicorn Group account manager
  • Site ID (SID) -> Corefy field sid -> where to find: issued by your Unicorn Group account manager
  • Token -> Corefy field token -> format: API token -> where to find: issued by your Unicorn Group account manager

Currency / Features are chosen in the connection form - check available currencies and services with your Corefy account manager.

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

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Merchant ID (MID) -> mid
  • Site ID (SID) -> sid
  • Token -> token
  • Currency / Features -> choose values available for your account

Success

You have connected Unicorn Group 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": "50475a8b-05b9-4b70-9674-86899a828c2e",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}
customer is optional - Unicorn Group's own connector reads customer.email/phone/address with a fallback (never a hard requirement), so a request with no customer object at all still goes through; missing values simply fall back to the Constants described below (or are sent empty if no constant is configured either).

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "01824bd8-889a-46c2-a14f-b6a36bc15474",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10.04,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "name@example.com",
        "phone": "+380991234567",
        "address": {
          "full_address": "Main street 1",
          "country": "US",
          "region": "NY",
          "city": "New York",
          "post_code": "10001"
        }
      }
    }
  }
}

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

Options

Currently available options (1)

  • ignore_callback - for cascading to work correctly, skips the generic callback processing step and relies only on an active status request to finalize the payment.
ignore_callback

What it does: when enabled, Corefy does not attempt to process an inbound callback hit for this connection, relying on an active status request (reconciliation) to finalize the payment instead.

When to use: enable only if instructed by Unicorn Group or your Corefy account manager - typically needed for cascading/reconciliation setups.

Default: false

Allowed values: true, false

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 first name (parsed from customer.name)
  • LAST_NAME -> customer last name (parsed from customer.name)
  • EMAIL -> customer.email
  • PHONE -> customer.phone
  • ADDRESS -> customer.address.full_address
  • CITY -> customer.address.city
  • REGION -> customer.address.region
  • COUNTRY -> customer.address.country
  • POST_CODE -> customer.address.post_code

Additional info

  1. Active reconciliation is available - both the asynchronous callback and an active status request can finalize the payment, unless ignore_callback is enabled.

  2. No recurring - this connector does not support saving/charging a token through Corefy.

  3. No hardcoded placeholder customer data is sent to the provider - missing fields fall back only to the Constants above (or are sent empty if no constant is configured either), never to fake values.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the Merchant ID, Site ID, and Token
  • Missing customer data -> set Constants (see Constants) or provide the fields directly in the API request
  • Refund fails with multiple attempts -> only one refund per payment is allowed
  • Not sure which account type to use? -> ask your Corefy account manager

Question

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