Cypix
Modern payment aggregator for your site
Supports in this guide: Payments, Payouts
Provider website: cypix.ru (unreachable at the time of writing - confirm the current website with your account manager before sharing it with anyone)
What you need to do for start processing transactions (brief summary)
- Choose account type
- Get your credentials (from Cypix)
- Connect in Dashboard
- Send an API request
Choose account type
Cypix 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 payouts -> choose Provider account
If you're not sure which one to use, confirm with your Corefy account manager.
Prerequisites: get from Cypix
Contact your Cypix account manager to get your account verified and receive the following credentials.
For H2H Merchant account:
- API Key -> Corefy field
api_key. - Secret Key -> Corefy field
secret_key-> used to sign every request. - Host -> Corefy field
host-> the API domain Cypix gives you.
For Provider account:
- Account ID -> Corefy field
account_id. - API Key -> Corefy field
api_key. - Secret Key -> Corefy field
secret_key. - Host -> Corefy field
host.
Payments processing (connect H2H Merchant account, create payment-invoice)
Connect H2H Merchant account in Corefy Dashboard
Step 1 - Open connection form
Open Cypix in the provider directory and press Connect at Cypix Provider Overview page in the New connection section. Choose H2H Merchant account.
Step 2 - Fill in fields and select settings
- API Key
- Secret Key
- Host
- 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 Cypix 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. Cypix 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_rub_hpp",
"currency": "RUB",
"amount": 10
}
}
}
Payment - MAX
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
"service": "payment_card_rub_hpp",
"currency": "RUB",
"amount": 10,
"customer": {
"reference_id": "cus_123",
"email": "johnsmith@gmail.com",
"phone": "+15551234567"
}
}
}
}
customer is entirely optional - email/phone are only used to enrich the sale, they never block it. If customer.address.country can't be resolved, Cypix receives RU as the default country code.
Important
This connector requires extra customer fields for some currencies, in addition to the usual card/amount data:
- EUR:
customer.address.region(falls back to country, then city) is sent as the customer's state. - AUD:
customer.date_of_birth,customer.email,customer.name,customer.phone, and a fullcustomer.address(full address/city/state/post code/country) are all expected - send them if you have them, to avoid declines. - CAD: the same set as AUD, plus
customer.address.streetseparately from the full address.
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 or Constants are configured for this connector.
Refunds
Cypix supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment).
Payouts processing (connect Provider account, create payout-invoice)
Connect Provider account in Corefy Dashboard
Step 1 - Open connection form
Open Cypix in the provider directory and press Connect at Cypix Provider Overview page in the New connection section. Choose Provider account.
Step 2 - Fill in fields and select settings
- Account ID
- API Key
- Secret Key
- Host
- Test Mode -> (enable if you are using sandbox credentials)
Success
You have connected Cypix Provider account!
First request to Corefy API (MIN)
What it does: creates a payout-invoice and sends funds directly to a card.
Payout - MIN
POST /api/payout-invoices
{
"data": {
"type": "payout-invoice",
"attributes": {
"reference_id": "0dde9e79-2c64-4703-adaf-93d710633401",
"service": "payment_card_rub",
"currency": "RUB",
"amount": 10,
"fields": {
"card_number": "4111111111111111"
}
}
}
}
Important
fields.card_number is required.
Payout - MAX
POST /api/payout-invoices
{
"data": {
"type": "payout-invoice",
"attributes": {
"reference_id": "3c6d2f8e-8a2a-4e7a-9b1a-2f6a7b9c0d1e",
"service": "payment_card_rub",
"currency": "RUB",
"amount": 10,
"customer": {
"reference_id": "cus_123",
"name": "John Smith"
},
"fields": {
"card_number": "4111111111111111"
}
}
}
}
customer is entirely optional - name, when sent, is transliterated to Latin and forwarded as the receiver's name.
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 or Constants are configured for this flow.
Additional info
- Callback routing is automatic - Corefy generates the callback/return URLs per transaction, nothing to configure in Cypix's own back-office.
FAQ / Troubleshooting
- Invalid credentials / auth error -> verify API Key/Secret Key/Host (and Account ID, for the Provider account) for the selected environment
- Card sale declined for EUR/AUD/CAD -> these currencies need extra customer fields - see the important note under Payments above
- Currency or service is not supported -> confirm allowed currencies/features in your Cypix account and in Corefy
Question
Still looking for help connecting your Cypix account? Please contact our support team!