Sola
The Specialist Payment Gateway for High-Risk & Regulated Industries in Europe
Website: sola.live
Set up H2H Merchant Account
Step 1: Create Merchant Account
To create an account send connection request at the sola.live or contact manager directly. Submit the required documents to verify your account and gain access.
Step 2: Get required credentials
Credentials that have to be issued:
- sola__project_id → Project ID
- sola__secret_key → Secret Key
- sola__currency → choose currency (You can set these parameters according to available currencies and features for your Sola wallets and services, but it's necessary to check details of the connection with your Corefy account manager.)
Question
"Having issues with your credentials?" Please contact our support team!
Connect H2H Merchant Account
Step 1. Connect H2H account at the Corefy Dashboard
Press Connect at Sola Provider Overview page in 'New connection' section and choose H2H Merchant account option to open Connection form.

Enter credentials:
- Project ID
- Secret Key
- Currency
Success
You have connected Sola H2H merchant account!
Provider Options
- Generate data for customer
- No (default) = only the customer data actually sent in the request (or resolved from constants, see below) is forwarded to the provider.
- Yes = after resolving customer data from the request and constants, any of the required fields (country, city, phone, first name, last name, email, address, zip, state, date of birth) that are still missing are filled in with plausible generated data before the request is sent to the provider. Data that was actually sent by the customer or resolved from constants is never overwritten.
API examples:
Minimum data set to create a payment invoices for payment_card_eur_hpp service
SALE
POST /api/payment-invoices HTTP/1.0
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "1f2aa3ca-abd8-4741-980d-4017ed30cb8c",
"service": "payment_card_eur_hpp",
"currency": "EUR",
"amount": 5,
"customer": {
"reference_id": "85af8385-d00e-4f58-ab1f-3a527fdf2d3b",
"name": "John Doe",
"email": "johndoe@mail.com",
"phone": "+2134234234523",
"date_of_birth": "1990-05-20",
"address": {
"country": "US",
"region": "New York",
"city": "Los Angeles",
"street": "5th Avenue 1",
"post_code": "10001"
}
},
"test_mode": false
}
}
}
Note
date_of_birth is passed to the provider as DD-MM-YYYY, converted automatically from the YYYY-MM-DD format used above. address.street is used as a fallback when the full address is not available.
Additional information
Constants

If some parameters are not sent in the transaction creation request, they will take the values from the set constants.
Here is a list of constants with their corresponding parameters:
- country → constant [customer_country]
- city → constant [customer_city]
- phone → constant [customer_phone]
- first_name → constant [customer_first_name]
- last_name → constant [customer_last_name]
- email → constant [customer_email]
- address → constant [customer_address]
- zip → constant [customer_zip]
- state → constant [customer_state]
- day_of_birth → constant [customer_day_of_birth] (format
DD-MM-YYYY)
Warning
address, zip, state and day_of_birth are sent to the provider as null if the customer does not send them, the Generate data for customer provider option is disabled, and the corresponding constant (customer_address, customer_zip, customer_state, customer_day_of_birth) is not configured. Enable the provider option or set the constants to avoid sending null for these fields.