Concryt
Payments and banking is what we do
Supports in this guide: Payments
Provider website: concryt.io
What you need to do for start processing transactions (brief summary)
- Choose account type
- Get your credentials (from Concryt)
- Connect in Dashboard
- Send an API request
Choose account type
Concryt can be connected in different ways (depending on your needs):
- If you do H2H card payments (card data sent directly) -> choose H2H Merchant account
- If you do BLIK or Open Banking payments (customer redirected to a hosted page) -> choose Merchant account
Concryt does not currently support payouts through Corefy. If you're not sure which one to use, confirm with your Corefy account manager.
Prerequisites: get from Concryt
Contact your Concryt account manager to get your account verified and receive the following credentials.
For H2H Merchant account:
- Merchant ID -> Corefy field
merchant_id. - Payment Key -> Corefy field
payment_key-> used to sign every request.
For Merchant account:
- Merchant ID -> Corefy field
merchant_id. - Control Key -> Corefy field
control_key-> used to sign every request. - API URL (optional) -> Corefy field
api_url-> leave as default unless your account manager tells you otherwise.
Payments processing (connect H2H Merchant account, create payment-invoice)
Connect H2H Merchant account in Corefy Dashboard
Step 1 - Open connection form
Open Concryt in the provider directory and press Connect at Concryt Provider Overview page in the New connection section. Choose H2H Merchant account.
Step 2 - Fill in fields and select settings
- Merchant ID
- Payment Key
- Test Mode -> (enable if you are using sandbox credentials)
Choose Currency / Features; check with your Corefy account manager which are enabled for your account.
Success
You have connected Concryt 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. Concryt may return a 3D Secure challenge redirect depending on the card.
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
}
}
}
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",
"date_of_birth": "1990-01-01",
"individual_tax_id": "12345678901",
"address": {
"country": "FR",
"region": "IDF",
"city": "Paris",
"street": "1 Main street",
"post_code": "75000"
}
}
}
}
}
customer is entirely optional - email/name/phone/date_of_birth/individual_tax_id/address fields each fall back to the matching Constant below, or are simply left blank on Concryt's side.
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
ignore_callback-> optional, boolean - for cascading to work correctly, excludes finalizing the payment from the asynchronous callback; Corefy then relies only on an active status request (reconciliation) to finalize it.
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)
CUSTOMER_EMAIL->customer.emailCUSTOMER_FIRST_NAME->customer.name(first part)CUSTOMER_LAST_NAME->customer.name(second part)CUSTOMER_PHONE->customer.phoneCUSTOMER_DATE_OF_BIRTH->customer.date_of_birthCUSTOMER_INDIVIDUAL_TAX_NUMBER->customer.individual_tax_idCUSTOMER_COUNTRY->customer.address.countryCUSTOMER_REGION->customer.address.regionCUSTOMER_CITY->customer.address.cityCUSTOMER_STREET->customer.address.streetCUSTOMER_POST_CODE->customer.address.post_code
Refunds
This connector supports partial and multiple refunds against the same payment.
Payments processing (connect Merchant account, create payment-invoice)
Connect Merchant account in Corefy Dashboard
Step 1 - Open connection form
Open Concryt in the provider directory and press Connect at Concryt Provider Overview page in the New connection section. Choose Merchant account.
Step 2 - Fill in fields and select settings
- Merchant ID
- Control Key
- API URL (optional)
- Test Mode -> (enable if you are using sandbox credentials)
Success
You have connected Concryt Merchant account!
First request to Corefy API (MIN)
What it does: creates a payment-invoice and redirects the customer to a hosted page to complete the payment with BLIK or Open Banking.
Payment - MIN
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
"service": "blik_pln_hpp",
"currency": "PLN",
"amount": 10
}
}
}
This connector also supports blik_eur_hpp, openbanking_pln_hpp, and openbanking_eur_hpp.
Payment - MAX
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
"service": "blik_pln_hpp",
"currency": "PLN",
"amount": 10,
"customer": {
"reference_id": "cus_123",
"name": "John Smith",
"email": "johnsmith@gmail.com",
"phone": "+15551234567",
"address": {
"country": "PL",
"region": "Mazowieckie",
"city": "Warsaw",
"full_address": "1 Main street",
"post_code": "00-001"
},
"metadata": {
"ip": "203.0.113.5",
"user_agent": "Mozilla/5.0",
"language": "en",
"screen_width": 1920,
"screen_height": 1080,
"color_depth": 24,
"timezone": "60",
"java_enabled": false,
"javascript_enabled": true,
"accept_header": "text/html"
}
}
}
}
}
customer is entirely optional - the customer.metadata.* browser/device fields fall back to the matching Constant below if not sent.
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 Options are configured for this flow.
Constants (fallback fields)
Configured per service (blik_<ccy>_hpp, openbanking_<ccy>_hpp).
Currently available constants (constant -> Corefy API field)
IP->customer.metadata.ipLANG->customer.metadata.languageUSER_AGENT->customer.metadata.user_agentACCEPT_HEADER->customer.metadata.accept_headerJAVASCRIPT_ENABLED->customer.metadata.javascript_enabledJAVA_ENABLED->customer.metadata.java_enabledCOLOR_DEPTH->customer.metadata.color_depthTIMEZONE->customer.metadata.timezoneSCREEN_HEIGHT->customer.metadata.screen_heightSCREEN_WIDTH->customer.metadata.screen_width
Refunds
This flow only supports full refunds - a partial refund is rejected outright.
Additional info
- Callback routing is automatic - Corefy generates the callback/return URLs per transaction, nothing to configure in Concryt's own back-office.
FAQ / Troubleshooting
- Invalid credentials / auth error -> verify Merchant ID and Payment Key/Control Key for the selected account type and environment
- Refund rejected on the Merchant account flow -> only full refunds are supported there, not partial - use the H2H Merchant account if you need partial refunds
- Currency or service is not supported -> confirm allowed currencies/methods in your Concryt account and in Corefy
Question
Still looking for help connecting your Concryt account? Please contact our support team!