
UnitePlat
Supports in this guide: Payouts
Provider website: uniteplat.com
What you need to do for start processing transactions (brief summary)
- Generate an RSA key pair yourself, share the public key with UnitePlat, and get UnitePlat's own public key in return
- Get your credentials (from UnitePlat)
- Connect in Dashboard
- Send an API request
Prerequisites: get from UnitePlat
Contact your UnitePlat account manager to get your account verified and receive the following credentials.
- Username -> Corefy field
username-> your account identifier at UnitePlat. - Service ID -> Corefy field
service_id-> the payout service identifier UnitePlat assigns to your account. - Private key -> Corefy field
private_key-> uploaded as a file -> this is your own private key: generate an RSA key pair yourself and share only the public key with your UnitePlat account manager. Corefy uses this private key to sign every outgoing request. - Public key -> Corefy field
public_key-> uploaded as a file -> this is UnitePlat's own public key, not yours: ask your UnitePlat account manager to provide it. Corefy uses it to verify that every response genuinely came from UnitePlat.
Example key-generation commands (for your own key pair)
openssl genrsa -out private.pem 1024
openssl rsa -in private.pem -pubout -out public.pem
RUB only.
Payouts processing (connect Provider account, create payout-invoice)
Connect Provider account in Corefy Dashboard
Step 1 - Open connection form
Open UnitePlat in the provider directory and press Connect at UnitePlat Provider Overview page in the New connection section.
Step 2 - Fill in fields and select settings
- Username ->
username - Service ID ->
service_id - Private key ->
private_key-> your own private key (upload as a file) - Public key ->
public_key-> UnitePlat's public key (upload as a file)
Success
You have connected UnitePlat Provider account!
First request to Corefy API (MIN)
What it does: creates a payout-invoice for a RUB card payout.
Payout - MIN
POST /api/payout-invoices
{
"data": {
"type": "payout-invoice",
"attributes": {
"reference_id": "a4e6a9d2-5f1c-4b7a-9c8d-1e2f3a4b5c6d",
"service": "payment_card_rub",
"currency": "RUB",
"amount": 1000,
"customer": {
"reference_id": "cus_123"
},
"fields": {
"card_number": "4111111111111111"
}
}
}
}
Important
fields.card_numberis required - the request fails before reaching UnitePlat if it's missing.- UnitePlat never sees Corefy's own
reference_id- a separate reference (a microsecond timestamp) is generated and sent to UnitePlat for every payout instead.
Payout - MAX
POST /api/payout-invoices
{
"data": {
"type": "payout-invoice",
"attributes": {
"reference_id": "f1a2b3c4-6d5e-4f7a-8b9c-0d1e2f3a4b5c",
"service": "payment_card_rub",
"currency": "RUB",
"amount": 1000,
"customer": {
"reference_id": "cus_123",
"phone": "+79991234567"
},
"fields": {
"card_number": "4111111111111111"
}
}
}
}
customer.phone is optional - when present, it's passed through to UnitePlat alongside the payout.
Extended request (MAX)
Why add extra fields (typical reasons): - Provide additional customer details for compliance/reconciliation - Include optional fields required by your specific flow
Refunds
UnitePlat does not support refunds - it only implements the Payouts side.
Additional info
-
Active reconciliation is available - Corefy can query UnitePlat for a payout's current status.
-
No recurring - this connector does not support saving/charging a token through Corefy.
-
Custom signed-XML protocol - every request/response between Corefy and UnitePlat is XML. Outgoing requests are signed with your own private key, and incoming responses are verified against UnitePlat's public key; this is handled automatically once both key files are uploaded, no further action needed on your side.
-
No Options or Constants are configured for this connector.
FAQ / Troubleshooting
- Invalid credentials / auth error -> verify the Username, Service ID, and that both the private key and public key files are correctly uploaded
- Connection fails with a signature error -> confirm the uploaded private key is your own and matches the public key shared with UnitePlat, and that the uploaded public key is genuinely UnitePlat's own
- Payout rejected for missing fields ->
fields.card_numberis required for every payout - Refund fails -> UnitePlat does not support refunds through Corefy
Question
Still looking for help connecting your UnitePlat account? Please contact our support team!