
RubinPay
Supports in this guide: Payments
Note
No independently verifiable public website could be confirmed for this provider - none is listed in OFT. Contact your account manager for onboarding details.
What you need to do for start processing transactions (brief summary)
- Get your credentials (from RubinPay)
- Connect in Dashboard
- Send an API request
Prerequisites: get from RubinPay
Contact your RubinPay account manager to get your account verified and receive the following credentials.
- Merchant private key -> Corefy field
merchant_private_key.
EUR, NOK, PLN, DKK, SEK, HUF, GBP.
Payments processing (connect H2H Merchant account, create payment-invoice)
Connect H2H Merchant account in Corefy Dashboard
Step 1 - Open connection form
Open RubinPay in the provider directory and press Connect at RubinPay Provider Overview page in the New connection section.
Step 2 - Fill in fields and select settings
- Merchant private key
- Currency / Features -> choose values available for your account (EUR, NOK, PLN, DKK, SEK, HUF, GBP)
Success
You have connected RubinPay 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.
Payment - MIN
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "ba343a17-2381-4954-8e97-8eb6c1d1065f",
"service": "payment_card_eur_hpp",
"currency": "EUR",
"amount": 10
}
}
}
Payment - MAX
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "054e2576-7b38-4e6c-bd57-8f66c14e920b",
"service": "payment_card_eur_hpp",
"currency": "EUR",
"amount": 10,
"customer": {
"reference_id": "cus_123",
"name": "Daria Kokotova",
"email": "test@mail.com",
"phone": "+351915032559",
"date_of_birth": "2000-10-13",
"address": {
"full_address": "Porto 357",
"country": "PT",
"city": "Porto"
}
}
}
}
}
Important
No Constants are configured for this connector - if a customer field is missing, it's simply not sent, unless generate_customer_date_of_birth is enabled (see Options below).
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, ignores RubinPay's asynchronous callback and relies only on an active status request to finalize the payment.generate_customer_date_of_birth-> optional, boolean - whencustomer.date_of_birthis missing, generates and sends a synthetic date of birth to RubinPay instead of leaving the field empty.
Refunds
RubinPay does not support refunds.
Additional info
- Active reconciliation is available - both the asynchronous callback and an active status request can finalize the payment, unless
ignore_callbackis enabled. - No recurring - this connector does not support saving/charging a token through Corefy.
FAQ / Troubleshooting
- Invalid credentials / auth error -> verify the merchant private key
- Currency or service is not supported -> confirm allowed currencies/features in your RubinPay account and in Corefy
- Refund fails -> RubinPay does not support refunds through Corefy
Question
Still looking for help connecting your RubinPay account? Please contact our support team!