Skip to content

Logo

AltitudePay

Accept Payments Anywhere, Anytime.

Website: www.altitudepayments.com

Set up Account H2H merchant account

Step 1: Create Merchant Account

To create an account send connection request at the www.altitudepayments.com/whyus or contact manager directly. Submit the required documents to verify your account and gain access.

Step 2: Get required credentials

Credentials that have to be issued:

  • Login
  • Control Key
  • Endpoint ID
  • Currency

Connect Merchant Account

Step 1. Connect H2H account at the Corefy Dashboard

Press Connect at AltitudePay Provider Overview page in 'New connection' section and choose H2H Merchant account option to open Connection form.

Connect

Enter credentials:

  • Login → login
  • Control Key → control_key
  • Endpoint ID → endpoint_id
  • Currency → choose currency (You can set these parameters according to available currencies and features for your AltitudePay wallets and services, but it's necessary to check details of the connection with your Corefy account manager.)

Success

You have connected AltitudePay H2H merchant account!

API examples:

Minimum data set to create a payment invoices for payment_card_eur_hpp service

SALE
POST /api/commerce/payment-invoices HTTP/1.0
{
  "data":{
    "type":"payment-invoice",
    "attributes":{
      "service":"payment_card_eur_hpp",
      "commerce_account":"hello_world",
      "currency":"EUR",
      "amount":2,
      "reference_id":"0f217d5c-0c07-49f6-ac0e-a59e1b305d1f",
      "flow":"charge",
      "gateway_options":{
        "cardgate":{
          "tokenize":""
        }
      },
      "customer":{
        "reference_id":"f303bdd5-51e9-4d9a-888d-cfd0cabb45db"
      },
      "test_mode":true,
      "options":{
        "allow_partially":false,
        "bypass_hpp":false,
        "send_operation_context_on_return":false
      },
      "service_fields":[
      ]
    }
  }
}

Maximum data set to create a payment invoices for payment_card_eur_hpp service

SALE
POST /api/commerce/payment-invoices HTTP/1.0
{
  "data":{
    "type":"payment-invoice",
    "attributes":{
      "service":"payment_card_eur_hpp",
      "commerce_account":"hello_world",
      "currency":"EUR",
      "amount":2,
      "reference_id":"034a4b84-e918-4943-875e-c99eb05c978a",
      "flow":"charge",
      "gateway_options":{
        "cardgate":{
          "tokenize":""
        }
      },
      "customer":{
        "reference_id":"27390eb2-4dc5-4e56-9ac1-fb5e1ce0a046",
        "name":"John Doe",
        "phone":"79001234567",
        "address":{
          "full_address":"vyl testova d. 34",
          "country":"UK",
          "region":"Kyivska obl",
          "city":"Kyiv",
          "street":"vyl testova",
          "post_code":"123987"
        }
      },
      "test_mode":true,
      "options":{
        "allow_partially":false,
        "bypass_hpp":false,
        "send_operation_context_on_return":false
      },
      "service_fields":[
      ]
    }
  }
}

Constants

Сonstants

If some parameters are not sent in the transaction creation request, they will take the values from the set constants.

Here is a list of constants with their corresponding parameters:

  • ADDRESS → customer [address] [address]
  • COUNTRY → customer [address] [country]
  • PHONE → customer [address] [phone]
  • EMAIL → customer [address] [email]
  • CITY → customer [address] [city]
  • POST_CODE → customer[address][post_code]
  • BROWSER_INFO → constant [browserInfo]
  • BROWSER_TZ_OFFSET → constant [browserTzOffset]
  • BROWSER_SCREEN_WIDTH → constant [browserScreenWidth]
  • BROWSER_SCREEN_HEIGHT → constant [browserScreenHeight]
  • BROWSER_COLOR_DEPTH → constant [browserColorDepth]
  • BROWSER_LANGUAGE → constant [browserLanguage]
  • BROWSER_JAVA_ENABLED → constant [browserJavaEnabled]
  • BROWSER_ACCEPT_HEADER → constant [browserAcceptHeader]
  • BROWSER_USER_AGENT → constant [browserUserAgent]
  • BROWSER_IP → constant [browserIp]

Provider Options

Provider_Options

  • ignore_callback → for cascading to work correctly, we exclude the possibility of finalizing payments using asynchronous callbacks, ignore the callback, do not change the status of the transaction on it in any way and rely only on the status request for finalization (Reconciliation)
  • use_default_browser_info → If the value is true, then the browser data is taken from constants. If the constants have a no values, then the browser data is taken from default values.
  • allow_callback_for_all_transaction_types → enabling this option means that Callback will be sent in different field “server_callback_url“ => “notify_url

Question

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