Skip to content

Logo

Hello Payment Solutions

Navigating global payments. We provide expertise in payment and settlement technologies around the globe

Supports in this guide: Payments, Payouts

Provider website: hellopsp.com

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

  1. Get your credentials (from Hello Payment Solutions)
  2. Connect in Dashboard
  3. Send an API request

Prerequisites: get from Hello Payment Solutions

Send a connection request at hellopsp.com/#contact or contact your account manager directly to get your account verified and receive the following credentials.

  • Login -> Corefy field login.
  • Password -> Corefy field password.
  • Salt -> Corefy field salt.
  • API Point -> Corefy field api_point.
  • Currency -> Corefy field currency -> one of JPY, KRW, UZS; each Provider account is locked to a single currency.

One Provider account is used for both Payments and Payouts, via card or bank transfer.

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

Connect Provider account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

  • Login
  • Password
  • Salt
  • API Point
  • Currency

Success

You have connected Hello Payment Solutions Provider account!

First request to Corefy API (MIN)

What it does: creates a payment-invoice. Card redirects to a hosted checkout; bank transfer returns bank account requisites for the customer to pay into.

Payment - MIN (bank transfer)

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "11fdab29-0fd0-40cb-a1c8-0d564850b70a",
      "service": "bank_transfer_jpy_invoice",
      "currency": "JPY",
      "amount": 1000
    }
  }
}

Payment - MAX (bank transfer)

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "2f3a4b5c-6d7e-4f80-8a01-2b3c4d5e6f70",
      "service": "bank_transfer_krw_invoice",
      "currency": "KRW",
      "amount": 10000,
      "customer": {
        "name": "John Doe",
        "email": "john@example.com"
      }
    }
  }
}

Important

  • For JPY, only customer.email is sent (or the EMAIL Constant); if neither is set, it's simply not sent.
  • For KRW, customer.name (split into first/last) and customer.email are sent (or the matching Constants); for UZS, no customer data is sent at all for Payments.
  • commission_type affects who pays the processing fee - see Options below.

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

  • commission_type -> optional, enum (USER_COMMISSION, MERCHANT_COMMISSION) - whether the processing fee is debited from the payer (USER_COMMISSION) or from you as the merchant (MERCHANT_COMMISSION).

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)

  • EMAIL -> customer.email -> available for bank_transfer_jpy_invoice and bank_transfer_krw_invoice
  • FIRST_NAME, LAST_NAME -> customer.name (split) -> available only for bank_transfer_krw_invoice

Refunds

Hello Payment Solutions does not support refunds.

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 and sends funds to a card or bank account, depending on the service.

Payout - MIN (card)

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "3a4b5c6d-7e8f-4091-8b02-3c4d5e6f7081",
      "service": "payment_card_jpy",
      "currency": "JPY",
      "amount": 1000,
      "fields": {
        "card_number": "4111111111111111"
      }
    }
  }
}

Important

fields.card_number is required for card payouts; the cardholder name is taken from customer.name or from your own card payout data.

Payout - MAX (bank transfer)

POST /api/payout-invoices 

{
  "data": {
    "type": "payout-invoice",
    "attributes": {
      "reference_id": "4b5c6d7e-8f90-4102-8c13-4d5e6f708192",
      "service": "bank_transfer_krw",
      "currency": "KRW",
      "amount": 10000,
      "fields": {
        "beneficiary_first_name": "John",
        "beneficiary_last_name": "Doe"
      }
    }
  }
}

Important

fields.beneficiary_first_name/fields.beneficiary_last_name (or fields.beneficiary_name) are required for bank transfer payouts; the bank itself is resolved automatically from the route.

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

  • commission_type -> optional, enum (USER_COMMISSION, MERCHANT_COMMISSION) - same meaning as on Payments, applied to the payout fee.

Additional info

  1. Active reconciliation is available - both Payments and Payouts support an active status request.
  2. No recurring - this connector does not support saving/charging a token through Corefy.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify Login, Password, Salt, and API Point
  • Currency or service is not supported -> each Provider account is locked to a single currency (JPY, KRW, or UZS) - confirm it matches the currency field you connected with
  • Payment declined for missing customer details -> for KRW, customer.name and customer.email are required; for JPY, customer.email is required
  • Refund fails -> Hello Payment Solutions does not support refunds through Corefy

Question

Still looking for help connecting your Hello Payment Solutions account? Please contact our support team!