Skip to content

Logo

Intervale

Supports in this guide: Payments

Provider website: intervale.ru

What you need to do for start processing transactions (brief summary)

  1. Get your credentials (from Intervale)
  2. Connect in Dashboard
  3. Send an API request

Prerequisites: get from Intervale

Contact your Intervale account manager to get your account verified and receive the following credentials.

  • Portal ID -> Corefy field portal_id.
  • Payment ID -> Corefy field payment_id.
  • API URL -> Corefy field api_url -> optional, overrides the default endpoint; leave blank unless Intervale instructs you to use a different one.

USD only.

Payments processing (connect H2H Merchant account, create payment-invoice)

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open Intervale in the provider directory and press Connect at Intervale Provider Overview page in the New connection section.

Step 2 - Fill in fields and select settings

  • Portal ID
  • Payment ID
  • API URL -> (optional)

Success

You have connected Intervale 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": "6be05631-8710-4b14-a369-1928a2b70eda",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10
    }
  }
}

Payment - MAX

POST /api/payment-invoices 

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "199be985-c243-478a-86a8-4b8c902e5bb6",
      "service": "payment_card_usd_hpp",
      "currency": "USD",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "email": "name@example.com"
      }
    }
  }
}

Important

customer.email is the only customer field this connector sends to Intervale; if missing and the EMAIL Constant isn't set either, it's simply left out of the request. No other customer fields (name, phone, address) are used.

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

Constants (fallback fields)

Constants are static values that Corefy can send to the provider instead of dynamic data from your API request, when those fields are missing in the request.

Priority (predictable rule): 1. If a value is present in the request -> Corefy uses the request value 2. Else if the constant is set -> Corefy uses the constant 3. Else -> provider may reject the request or apply its defaults (depends on provider)

Currently available constants (constant -> Corefy API field)

  • EMAIL -> customer.email

Refunds

Intervale does not support refunds.

Additional info

  1. Active reconciliation is available, and a callback is also processed - both the asynchronous callback and an active status request can finalize the payment.
  2. No recurring - this connector does not support saving/charging a token through Corefy.
  3. USD only - this connector does not currently support any other currency.

FAQ / Troubleshooting

  • Invalid credentials / auth error -> verify the Portal ID and Payment ID
  • Currency or service is not supported -> only USD is available for this connector
  • Refund fails -> Intervale does not support refunds through Corefy

Question

Still looking for help connecting your Intervale account? Please contact our support team!