PayRacks

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Merchant ID -> merchant_id
• Application Key -> application_key
• Merchant Secret -> merchant_secret
• Gateway -> gateway (optional, predefined PayRacks processing gateway; leave empty to let PayRacks select it)
• Test Mode -> (enable if you are using sandbox credentials)

Choose Currency and Features, and keep Method set to payment_card. You can set these parameters according to available currencies and features for your PayRacks account, but it is necessary to check details of the connection with your Corefy account manager.

First request to Corefy API (MIN)

What it does: creates a payment-invoice.

PayRacks requires the customer's email and country for every card payment. Send them in the request (customer.email, customer.address.country) or set the CUSTOMER_EMAIL and CUSTOMER_COUNTRY constants on the connection (see "Constants" below). The cardholder name is taken from the card form.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8afec793-9b41-4dc4-b281-c76cc54ffb89",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "johnsmith@gmail.com",
        "phone": "1234567890",
        "address": {
          "country": "MX",
          "city": "Mexico City",
          "full_address": "123 Main St.",
          "post_code": "12345"
        }
      }
    }
  }
}

Payment - MAX

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "06fa1ea9-8a5b-4dbc-b67b-6236b3b9af3d",
      "service": "payment_card_eur_hpp",
      "currency": "EUR",
      "amount": 100,
      "customer": {
        "reference_id": "cus_123",
        "name": "John Doe",
        "email": "johnsmith@gmail.com",
        "phone": "1234567890",
        "date_of_birth": "1990-01-31",
        "address": {
          "country": "MX",
          "region": "CMX",
          "city": "Mexico City",
          "full_address": "123 Main St.",
          "post_code": "12345"
        }
      }
    }
  }
}

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.

So, if a field is missing in the API request, Corefy can take the value from the configured Constants.

After the successful connection, fill in constants for necessary routes in editing menu.

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)

• CUSTOMER_LAST_NAME -> customer.name (last name part, used when the cardholder name has no last name)
• CUSTOMER_EMAIL -> customer.email
• CUSTOMER_PHONE -> customer.phone (digits only are sent to PayRacks)
• CUSTOMER_DATE_OF_BIRTH -> customer.date_of_birth (format MM/DD/YYYY)
• CUSTOMER_COUNTRY -> customer.address.country (ISO 3166-1 alpha-2, e.g. MX)
• CUSTOMER_REGION -> customer.address.region
• CUSTOMER_CITY -> customer.address.city
• CUSTOMER_POST_CODE -> customer.address.post_code
• CUSTOMER_FULL_ADDRESS -> customer.address.full_address (or customer.address.street)