Ragapay

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

Open Ragapay in the provider directory and press Connect at Ragapay Provider Overview page in the New connection section. Choose H2H Merchant account.

Step 2 - Fill in fields and select settings

• Client Key
• Client Pass

Choose Currency / Features; check with your Corefy account manager which are enabled for your 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. Ragapay 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_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

This connector also supports USD.

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "6795502c-e27d-4d07-85e0-93245aab9a3f",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 10,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Smith",
        "email": "johnsmith@gmail.com",
        "phone": "+15551234567",
        "date_of_birth": "1990-01-01",
        "address": {
          "country": "FR",
          "region": "IDF",
          "city": "Paris",
          "full_address": "1 Main street",
          "post_code": "75000"
        }
      }
    }
  }
}

customer is entirely optional. For the first/last name sent to Ragapay, the priority is: customer.name first, then the name embossed on the card, then the Constants below. customer.email (or the matching constant) is effectively required - it's used to sign every request to Ragapay, so a sale without either is likely to fail.

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

• auth -> optional, boolean - authorization mode: holds funds without capturing them, instead of an immediate sale.
• ignore_callback -> optional, boolean - for cascading to work correctly, excludes finalizing the payment from the asynchronous callback; Corefy then relies only on an active status request (reconciliation) to finalize it.
• allow_ipv6 -> optional, boolean - sends the customer's real IPv6 address to Ragapay as-is; when disabled (default), an IPv6 client IP is replaced with a placeholder IP (or the IP constant, if set) because Ragapay expects IPv4.

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)

• PAYER_FIRST_NAME -> customer.name (first part)
• PAYER_LAST_NAME -> customer.name (second part)
• PAYER_MIDDLE_NAME -> used only when neither customer.name nor the card's embossed name is available
• PAYER_EMAIL -> customer.email
• PAYER_PHONE -> customer.phone
• PAYER_BIRTH_DATE -> customer.date_of_birth
• PAYER_COUNTRY -> customer.address.country
• PAYER_STATE -> customer.address.region
• PAYER_CITY -> customer.address.city
• PAYER_ADDRESS -> customer.address.full_address
• PAYER_ZIP -> customer.address.post_code
• IP -> fallback IP sent instead of the customer's real IP, only when it's IPv6 and allow_ipv6 is disabled
• TERM_URL_TARGET -> the browser target (e.g. same window/frame vs. a new one) used when redirecting the customer back after a 3D Secure challenge; defaults to the same window if not set

Refunds

Ragapay supports full refunds only (no partial refunds), and only one refund per payment.

Recurring (save and charge a token)

This connector supports saving the card as a token during a sale (via Corefy's standard tokenize-on-sale request) and later charging that same token without sending full card data again.