
Hashconnect
Hashconnect Internet Acquiring
Supports in this guide: Payments
Provider website: hashconnect.eu
What you need to do for start processing transactions (brief summary)
- Get your credentials (from Hashconnect)
- Generate and share a key pair
- Connect in Dashboard
- Send an API request
Prerequisites: get from Hashconnect
Log in to the Hashconnect merchant dashboard (or contact your account manager) to get your account verified and receive the following credentials.
- Site ID -> Corefy field
site_id.
Generate your own RSA key pair:
openssl genrsa -out private_key.pem 2048
openssl rsa -in private_key.pem -pubout -outform PEM -out public_key.pem
- Private key -> Corefy field
key-> uploadprivate_key.pem.
Important
Be sure to check with your account manager if you require a white list of IPs, and if so, specify IP addresses from the Corefy list.
RUB only.
Payments processing (connect H2H Merchant account, create payment-invoice)
Connect H2H Merchant account in Corefy Dashboard
Step 1 - Open connection form
Open Hashconnect in the provider directory and press Connect at Hashconnect Provider Overview page in the New connection section.
Step 2 - Fill in fields and select settings
- Site ID
- Private key -> upload
private_key.pem - Test Mode -> (enable if you are using sandbox credentials)
Success
You have connected Hashconnect 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. Hashconnect may return a 3D Secure challenge redirect depending on the card.
Payment - MIN
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "1a2b3c4d-5e6f-4a7b-8c91-2d3e4f5a6b7c",
"service": "payment_card_rub_hpp",
"currency": "RUB",
"amount": 100
}
}
}
Payment - MAX
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "2b3c4d5e-6f7a-4b8c-8d02-3e4f5a6b7c8d",
"service": "payment_card_rub_hpp",
"currency": "RUB",
"amount": 100,
"customer": {
"reference_id": "cus_123",
"email": "test@example.com",
"phone": "+79991234567"
}
}
}
}
Important
- The amount must be between
10and9999999.99in the service's currency. - If
customer.email,customer.phone, or the client IP aren't available, a fixed placeholder value is sent to Hashconnect instead of leaving the field empty - there is no Constants mechanism for this connector. - Payments that can't be determined as 3D Secure or non-3D Secure upfront are declined immediately, without being sent to Hashconnect.
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
Refunds
Hashconnect supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment).
Additional info
- Active reconciliation is available - an active status request can finalize the payment in addition to the asynchronous callback.
- No recurring - this connector does not support saving/charging a token through Corefy.
- No Options or Constants are configured for this connector.
FAQ / Troubleshooting
- Invalid credentials / auth error -> verify the Site ID and private key for the selected environment (
test_mode) - Payment declined before reaching Hashconnect -> this happens when 3D Secure enrollment can't be determined upfront for the card; try a different card
- Currency or service is not supported -> confirm allowed currencies/features in your Hashconnect account and in Corefy - only
RUBis available - Refund fails with multiple attempts -> only one refund per payment is allowed
Question
Still looking for help connecting your Hashconnect account? Please contact our support team!