API
Integration Guide
This page provides information to help you integrate CellPoint Digital's Velocity Payment Orchestration Platform (POP) with your application using the Velocity application programming interface (API).
A single integration with the Velocity POP via API provides a variety of payment options for merchant websites and mobile applications. API integration is suitable for mobile applications or websites that have Payment Card Industry Data Security Standard (PCI DSS) requirements. The API integration process is easy, and the CellPoint team provides support for it.
For API reference, see API Payment Operations in our Reference section.
How it works
To begin accepting payments, you should understand our basic API calls:
<initialize-payment>
| FOP curation: This uses the context of the order to determine which forms of payment should be offered. It will also initialize your session and transaction and provide those IDs back to you for the next steps of the payment flow.
<pay>
| APMs: This is an optional call used when certain forms of payment have been selected by the user. These are typically redirect APMs such as PayPal and eWallets like Apple Pay and Google Pay.
<authorize-payment>
| Authorize: This triggers the authorization workflow for the provided payment with the order and payment details provided. This call has secondary uses when interrupts such as 3DS Challenges are triggered.
Expand this section for a diagram of the workflow for all major API operations.

Operations
Velocity API supports the following operations. Expand each section for more information on the operation:
Initialize
Expands this section for more on Initialize.
When you send an Initialize (initialize-payment
) POST request, the Velocity API initializes the payment process, and it returns information about the transaction (such as transaction ID and amount) and the configured payment methods or card types the customer can use.
The Initialize response contains these types of information:
- Merchant configuration - The client-config element provides merchant-set configurations, like the callback URL.
- Transaction information - The transaction element contains information about the transaction, such as the transaction ID and amount.
- Card information - The cards element provides the configured payment methods that the customer can use.
Prerequisite - Work with your CellPoint Digital sales representative or account manager to sign up, set up your test account, and access your testing credentials.
For API reference, see Initialize.
Authorize
Expand this section for more on Authorize.
The Authorize (authorize-payment
) operation authorizes a transaction. There are alternative request formats depending on the payment methods selected.
Prerequisite - Work with your CellPoint Digital sales representative or account manager to sign up, set up your test account, and access your testing credentials.
Response - Velocity API's Authorize response confirms successful authorization; otherwise, it has minimal data. Most of the relevant data in response to a proper authorization is provided in the Webhook body. For example, a Webhook can include authorization approval code, address verification, fraud results, and 3DS results. For more information, see our Webhooks integration guide.
3-D Secure (3DS) - Part of CellPoint's 3DS flow can be triggered by the Authorize operation. If you receive an Authorize response with the 3DS trigger, see our 3-D Secure integration guide for more information.
For API reference, see Authorize.
Pay
Expand this section for more on Pay.
The Pay operation is normally used for an alternative payment method (APM) payment. The request is an internal request from a merchant’s portal to the Velocity API when a customer initializes a payment. The operation does the following:
- Retrieve information about how to proceed with the payment or PSP confirmation. This information gives an idea about the parameters required to authorize a transaction.
- Ensure that a complete audit trail is maintained for each payment transaction.
- It can also return different responses depending on the type of payment, such as 3DS, non-3DS, wallet, other APM, or stored card.
Note: Merchants are not required to send a Pay request in the following situations:
- Card payment.
- Using stored card information that is in Velocity's store vault.
Prerequisite - Work with your CellPoint Digital sales representative or account manager to sign up, set up your test account, and access your testing credentials.
The structure of the Pay response depends on the type of payment being made.
After using the Pay operation, merchants must send an Authorize request. See Authorize for details.
For API reference, see Pay.
Capture
Expand this section for more on Capture.
The Capture (capture-payment
) operation captures an authorized transaction. Use it to facilitate a complete capture or a partial capture, depending on the value of the amount
field in your request. (A partial capture uses an amount
that's greater than 0
and less than the authorized amount.)
Note: Only use the Capture operation if you have enabled manual capture. Do not use it if you have enabled auto-capture.
Prerequisite - Work with your CellPoint Digital sales representative or account manager to sign up, set up your test account, and access your testing credentials.
Integration notes:
- When sending a Capture request, include transaction details from your successful Authorize request.
- The Velocity API returns a Capture response confirming if the request succeeded or failed. If your Capture request was successful, the Velocity server returns a Capture response containing the transaction ID and
status code="1000”
.
For API reference, see Capture.
Ticket-level Capture
Expand this section for more on Ticket-level Capture.
The Ticket-level Capture (update-order-data
) operation is applicable to use by an airline; it facilitates automatic ticket-level captures. After updating Airline Itinerary Data (AID), Velocity captures the transaction amount internally and passes the information to PSPs for payment processing. After that, it is passed to the merchant system. You do not need to use the Capture operation.
Note: You do not need to use the Capture operation if you are using this operation.
Prerequisite - Work with your CellPoint Digital sales representative or account manager to sign up, set up your test account, and access your testing credentials.
Integration notes:
You must send a separate Ticket-level Capture request for each transaction associated with the order number (order-no
). Each request contains one or more line-item
objects; each line-item
object is associated with a distinct order-ref
value (the ticket/emd number). See the example below:
Order #PNRABC: $1000 | UATP Card $100 Request 1 | VISA Card $900 Request 2 | |
---|---|---|---|
Transaction 1 | Transaction 2 | ||
Ticket Number 1 line-item | 50 | 50 | 0 |
Ticket Number 2 line-item | 475 | 25 | 450 |
Ticket Number 3 line-item | 475 | 25 | 450 |
For API reference, see Ticket-level Capture.
Reversal / Refund
Expand this section for more on Reversal / Refund.
The Reversal/Refund (refund
) operation reverses or refunds a transaction. To refund multiple transactions to a customer in a single request, use the Bulk Refund operation.
Please note:
- The Refund (
refund
) operation voids an authorized transaction or refunds a captured transaction based on the status of the transaction. - If refunding a captured transaction, you can provide a partial refund or a complete refund. The
amount
field can take values equal to or less than the captured amount. If you do not specify an amount, a customer receives the complete refund. - If voiding an authorized transaction, you must void the full authorized amount.
Prerequisites:
- Work with your CellPoint Digital sales representative or account manager to sign up, set up your test account, and access your testing credentials.
- Do one or both of the following:
- Use the Authorize operation to authorize a transaction, or
- Use the Capture operation to capture a transaction.
For API reference, see Reversal / Refund.
Bulk Refund
Expand this section for more on Bulk Refund.
The Bulk Refund (bulk-refund
) operation refunds multiple transactions to a customer in a single request. To reverse or refund a single transaction, use the Reversal/Refund operation.
Please note:
- This operation voids an authorized transaction or refunds a captured transaction based on the status of the transaction.
- If refunding a captured transaction, you can provide a partial refund or a complete refund. The
amount
field can take values equal to or less than the captured amount. If you do not specify an amount, a customer receives the complete refund. - If voiding an authorized transaction, you must void the full authorized amount.
Prerequisites:
- Work with your CellPoint Digital sales representative or account manager to sign up, set up your test account, and access your testing credentials.
- Do one of the following:
- Use the Authorize operation to authorize a transaction, or
- Use the Capture operation to capture a transaction.
- Repeat the step above to authorize or capture at least one more transaction.
For API reference, see Bulk Refund.
Get Payment Methods
Expand this section for more on Get Payment Methods.
The Get Payment Methods operation returns a list of payment methods with which a customer is eligible to pay. This eligibility is based on the Curated Payment Business Rule that is applicable to the transaction.
Prerequisite - Work with your CellPoint Digital sales representative or account manager to sign up, set up your test account, and access your testing credentials.
For API reference, see Get Payment Methods.
Get Transaction Status
Expand this section for more on Get Transaction Status.
The Get Transaction Status operation (get-transaction-status
) returns a transaction status based on its transaction ID, or a session status based on its session ID. The operation is useful to reverify a transaction status when, for example, the Authorize operation does not show a success response due to network issues or after redirection flow.
Please note:
- CellPoint Digital recommends integrating Get Transaction Status, but it is optional.
- You can configure this operation to view a transaction's status on your web portal or on your server.
Prerequisites:
- Work with your CellPoint Digital sales representative or account manager to sign up, set up your test account, and access your testing credentials.
- Use the Initialize, Authorize, or Capture operation to start a payment transaction (and, optionally, capture it).
Integration notes:
- You can change whether you request a transaction status or a session status by varying the content of the request.
- Once you have sent your Get Transaction Status request, Velocity API sends a response containing information about the transaction or the session whose status you have requested.
For API reference, see Get Transaction Status.
Get Payment Summary
Expand this section for more on Get Payment Summary.
The Get Payment Summary operation (get-payment-summary
) retrieves the decrypted summary of one or more payments, including the masked card numbers from various wallets.
Get Payment Summary is only applicable to wallet integration. For instance, if you have integrated Apple Pay or Google Pay and want to show the masked card number to the customer, you can use this operation.
Prerequisites:
- Work with your CellPoint Digital sales representative or account manager to sign up, set up your test account, and access your testing credentials.
- Do one or both of the following:
- Use the Authorize operation to authorize a transaction, or
- Use the Capture operation to capture a transaction.
For API reference, see Get Payment Summary.
Get Installment Plans
Expand this section for more on Get Installment Plans.
The Get Installment Plans operation returns a list of installment plans available for a selected credit card. It is not applicable to wallet integrations.
Prerequisites:
- Work with your CellPoint Digital sales representative or account manager to sign up, set up your test account, and access your testing credentials, and set up your account to allow for installment payments.
- Follow the Installments guide to send an Initialize request for a payment option that is eligible for installments.
For more information on integrating this operation see our Installments integrations guide.
For API reference, see Get Installment Plans.
FX: Offer Criteria
Expand this section for more on FX: Offer Criteria.
The FX: Offer Criteria operation (foreignexchange/offers
) is used as part of the Foreign Exchange (FX) feature. The operation returns currency exchange rates for a selected card's currency.
Prerequisite - Work with your CellPoint Digital sales representative or account manager to sign up, set up your test account, and access your testing credentials.
For more information on the integration and use of this API operation, see the Foreign Exchange (FX) integration guide.
For API reference, see FX: Offer Criteria.
Pay By Link (PBL)
Expand this section for more on Pay By Link (PBL).
You can use the Pay By Link (PBL) operation to create a payment link for a customer using Velocity POP. When a customer clicks the payment link, it directs them to a hosted payment page for them to complete their payment. This operation also supports generation of payment links in bulk, up to 20 payment links at a time.
Prerequisite - Work with your CellPoint Digital sales representative or account manager to sign up, set up your test account, and access your testing credentials.
Response - The response contains one or more payment links with the expiration of each link configured in the request body of the API. Each payment link is mapped to its request using the reference
value present in both request and response.
For API reference information, see Pay By Link (PBL).
Deactivate PBL
Expand this section for more on Deactivate PBL.
You can use Velocity API's Deactivate PBL operation to deactivate a payment link that you previously generated using the Pay By Link (PBL) operation. For information on generating a payment link, see the Pay By Link (PBL) section above.
Prerequisite - Work with your CellPoint Digital sales representative or account manager to sign up, set up your test account, and access your testing credentials.
For API reference information, see Deactivate PBL.
Features
This section describes the features available through Velocity API integration.
Fraud Detection
When a transaction is marked as fraud, CellPoint Digital treats similar transactions in the same manner regardless of the party that marked it as fraud.
For example, if you elect to disable a card payment method after one failed attempt or one fraud transaction, and a specific card transaction is marked as fraud by any system (a PSP, an acquirer, or a fraud system provider), then CellPoint Digital will disable the credit/debit card FOP.
3-D Secure (3DS)
For extra fraud protection, the 3-D Secure 2.0 (3DS2) protocol requires certain information about the customer’s device to recognize the overall risk for a given transaction. This process of collecting device information for risk-based analysis is called device fingerprinting.
Due to merchant requirements across multiple regions, the system must identify what Device Data Collection (DDC) needs on a platform level. To fulfill this requirement, the POP system should be able to support this feature for 3DS2-opted payments.
For more information, see our 3-D Secure (3DS) integration guide.
Split Payments
CellPoint's Velocity API lets a customer split their payment between multiple available payment methods. The customer may split payments for a single transaction or for a payment session with multiple transactions. The merchant configures the business rules for this process.
See our Split Payments integration guide for more information.
Installments
You can use CellPoint Velocity's Installments feature to allow customers to make payments in installments. This feature is applicable to an API integration for credit card transactions where the cardholder's country is the same as the pricing country.
You can use the Vision platform to configure the card types and customers for whom this feature is available and to set the maximum number of months a customer may select.
See our Installments integration guide for more information.
Foreign Exchange (FX)
The Foreign Exchange (FX) Service operates through Dynamic Currency Conversion (DCC) to fetch foreign exchange rates from a third-party provider, supporting transactions in currencies a customer may prefer. This feature is applicable to an API integration for transactions using MasterCard or Visa, and it requires a partnership with a third-party FX provider.
For more information, see our Foreign Exchange (FX) integration guide.
For API reference, see Initialize Response Parameters, FX: Offer Criteria, and Authorize in Reference.
Display Order Data
Velocity API supports the ability for merchants from specific domains, such as airlines or hotels, to display booking information to customers after they make payment.
To use this feature, the merchant includes the orders
element in the Initialize request for a new payment transaction. Once the payment is initialized, Velocity provides order data in addition to the required transaction information. For more information, contact your CellPoint Digital sales representative or account manager.
For API reference, including a sample request with the orders
element, see Initialize in Reference.
Airline Itinerary Data (AID)
Airline Itinerary Data (AID) can be used in API integrations to qualify a card purchase for an advantageous interchange rate. It is also used heavily in embedded fraud flows.
This feature is available if the merchant qualifies for airline interchange rates and uses an airline MCC (Merchant Category Code). To use it, the merchant includes the airline-data
element (inside the orders
element) in the Initialize request for a new payment transaction. For more information, contact your CellPoint Digital sales representative or account manager.
For API reference, including a sample request containing AID, see Initialize in Reference.
Updated 10 days ago