Monobank
Make business effortless with mono
Supports in this guide: Payments
Provider website: monobank.ua
What you need to do for start processing transactions (brief summary)
- Choose account type
- Get your credentials (from Monobank)
- Connect in Dashboard
- Send an API request
Choose account type
Monobank 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 redirect payments (Monobank's own hosted invoice page) -> choose Provider account
If you're not sure which one to use, confirm with your Corefy account manager.
Prerequisites: get from Monobank
Submit a connection request at monobank.ua/contacts or contact your Monobank account manager directly to get your account verified and receive the following credentials.
For H2H Merchant account:
- Merchant ID -> Corefy field
merchant_id-> this is a value you choose yourself to identify your account in Corefy, not something Monobank issues. - API Token -> Corefy field
api_token. - Webhook Key -> Corefy field
webhook_key-> get it with aGETrequest tohttps://api.monobank.ua/api/merchant/pubkey, with headerX-Token: <your API Token>- the response body is the key.
For Provider account:
- API Token -> Corefy field
api_token.
Payments processing (connect H2H Merchant account, create payment-invoice)
Connect H2H Merchant account in Corefy Dashboard
Step 1 - Open connection form
Open Monobank in the provider directory and press Connect at Monobank Provider Overview page in the New connection section. Choose H2H Merchant account.
Step 2 - Fill in fields and select settings
- Merchant ID
- API Token
- Webhook Key
- Test Mode -> (enable if you are using sandbox credentials)
Choose Currency and Features. EUR, UAH, and USD are confirmed; check with your Corefy account manager which are enabled for your account.
Success
You have connected Monobank 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": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
"service": "payment_card_uah_hpp",
"currency": "UAH",
"amount": 10
}
}
}
Payment - MAX
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
"service": "payment_card_uah_hpp",
"currency": "UAH",
"amount": 10
}
}
}
This connector doesn't use customer at all on this flow - there's nothing to add beyond reference_id/service/currency/amount. CVV is required. This connector also supports EUR and USD (use payment_card_eur_hpp/payment_card_usd_hpp as the service code).
Important
Only full refunds are supported - there's no partial refund on this connector. For EUR/USD transactions specifically, a refund can only be processed once the original transaction has settled; refunding before that fails.
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.
Payments processing (connect Provider account, create payment-invoice)
Connect Provider account in Corefy Dashboard
Step 1 - Open connection form
Open Monobank in the provider directory and press Connect at Monobank Provider Overview page in the New connection section. Choose Provider account.
Step 2 - Fill in fields and select settings
- API Token
Success
You have connected Monobank Provider account!
First request to Corefy API (MIN)
What it does: creates a payment-invoice and returns a redirect link to Monobank's own hosted invoice page.
Payment - MIN
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
"service": "monobank_uah_hpp",
"currency": "UAH",
"amount": 10
}
}
}
Payment - MAX
POST /api/payment-invoices
{
"data": {
"type": "payment-invoice",
"attributes": {
"reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
"service": "monobank_uah_hpp",
"currency": "UAH",
"amount": 10
}
}
}
This connector doesn't use customer at all on this flow either. monobank_uah_hpp and payment_card_uah_hpp create the exact same kind of hosted invoice on Monobank's side - they're functionally identical; pick whichever one matches how you want it labeled/categorized in your own reporting.
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 URL per transaction for both account types, nothing to register in Monobank's own back-office.
- Card tokenization is automatic on the H2H flow. After a successful sale, Corefy saves the card as a token with Monobank; a later sale with the same card number on the same account is submitted using that saved token instead of raw card data again. This is fully automatic - there's nothing to configure.
FAQ / Troubleshooting
- Invalid credentials / auth error -> verify credentials for the selected environment and account type
- Refund rejected -> only full refunds are supported, and
EUR/USDtransactions must be settled before they can be refunded - Currency or service is not supported -> confirm allowed currencies/features in your Monobank account and in Corefy
- Not sure which account type to use? -> ask your Corefy account manager
Question
Still looking for help connecting your Monobank account? Please contact our support team!