AltitudePay

Connect H2H Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Login
• Control Key
• Endpoint ID
• Multi Currency Integration
• API URL (optional)
• Test Mode -> (enable if you are using sandbox credentials)

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. AltitudePay may return a redirect for an authentication challenge, 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
    }
  }
}

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": "Ile-de-France",
          "city": "Paris",
          "full_address": "1 Main street",
          "post_code": "75000"
        },
        "metadata": {
          "ip": "203.0.113.5"
        }
      }
    }
  }
}

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, excludes finalizing the payment from the asynchronous callback; Corefy then relies only on an active status request (reconciliation) to finalize it.
• use_default_browser_info -> optional, boolean - when the customer's real browser data isn't available, falls back to the BROWSER_* Constants below (and ultimately to a fixed placeholder device profile) instead of sending no browser data at all.
• allow_callback_for_all_transaction_types -> optional, boolean - changes which field receives the callback URL on AltitudePay's side (notify_url instead of the default server_callback_url); only change this if your account manager tells you to.

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)

• ADDRESS -> customer.address.full_address
• CITY -> customer.address.city
• POST_CODE -> customer.address.post_code
• COUNTRY -> customer.address.country
• PHONE -> customer.phone
• EMAIL -> customer.email
• BROWSER_INFO, BROWSER_TZ_OFFSET, BROWSER_SCREEN_WIDTH, BROWSER_SCREEN_HEIGHT, BROWSER_COLOR_DEPTH, BROWSER_LANGUAGE, BROWSER_JAVA_ENABLED, BROWSER_ACCEPT_HEADER, BROWSER_USER_AGENT, BROWSER_IP -> fallback browser/device fingerprint values, used only when use_default_browser_info is enabled and real browser data isn't available.

Refunds

This connector supports partial refunds, but only one refund per payment (no multiple partial refunds against the same payment).

Connect Merchant account in Corefy Dashboard

Step 1 - Open connection form

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

Step 2 - Fill in fields and select settings

• Login
• Control Key
• Endpoint ID
• Multi Currency Integration
• API URL (optional)
• Test Mode -> (enable if you are using sandbox credentials)

First request to Corefy API (MIN)

What it does: creates a payment-invoice and redirects the customer to a hosted page to complete the purchase with Apple Pay or Google Pay.

Payment - MIN

POST /api/payment-invoices

{
  "data": {
    "type": "payment-invoice",
    "attributes": {
      "reference_id": "8e3dbbb0-17af-4c9a-bedb-93bdac6900a2",
      "service": "applepay_eur_hpp",
      "currency": "EUR",
      "amount": 10
    }
  }
}

This connector also supports googlepay_eur_hpp, and both methods in AUD/USD (applepay_aud_hpp, googlepay_aud_hpp, applepay_usd_hpp, googlepay_usd_hpp).

Payment - MAX

POST /api/payment-invoices

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

customer is entirely optional - everything you don't send falls back to the Constants below, or to a fixed placeholder address/contact AltitudePay accepts as a default.

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 are configured for this flow.

Constants (fallback fields)

Configured per service (applepay_<ccy>_hpp, googlepay_<ccy>_hpp).

Currently available constants (constant -> Corefy API field)

• ADDRESS -> customer.address.full_address
• CITY -> customer.address.city
• ZIP -> customer.address.post_code
• COUNTRY -> customer.address.country
• PHONE -> customer.phone
• EMAIL -> customer.email
• FIRST_NAME / LAST_NAME -> customer.name
• IP -> customer.metadata.ip
• URL -> not currently used in the request