How To Start
| Requirement | Details |
|---|---|
| Connection Type | WebSocket (WSS) |
| UAP Base URL | wss://epxpay-stg.nabancard.io/staging/ |
| Authentication | Four-part key + MAC/TIC via query parameter |
| Supported Hardware | All Ingenico Tetra terminals (DESK, LANE, MOVE, LINK) |
- Sign up for a free North Developer account.
- Purchase a test terminal or contact us to use your own device. Test credentials (four-part key and MAC/TIC) will be provided to you and can be referenced on the Credentials page.
- Connect your Ingenico terminal to the network. The terminal will automatically connect to the cloud—no IP configuration required.
- Use the WebSocket integration steps below to connect and process transactions. The XML request structure is documented in the XML Request Fields section.
- When development is complete, contact us for certification. Once certified, production credentials will be provided.
Step 1: Establish WebSocket Connection
The Ingenico SI Cloud solution communicates using a WebSocket connection. To establish a connection, include your terminal credentials as a merchantId query parameter.
Connection URL Format
Example Connection URL
| Component | Description |
|---|---|
9001-999999-1-1 | Your four-part key (CUST_NBR-MERCH_NBR-DBA_NBR-TERMINAL_NBR) |
MAC123456789 | Your MAC or TIC value |
Step 2: Send a Transaction
Once the WebSocket connection is established, send transactions as JSON objects with a message field containing the XML payload.
Request Format
Sale Transaction Example (CCR1)
Step 3: Handle the Response
The terminal will respond with XML messages. Validate transaction responses by checking for the AUTH_RESP field.
Transaction Response Example
A successful transaction response will include the AUTH_RESP field:
Key Response Fields
| Field | Description |
|---|---|
AUTH_RESP | Response code. 00 indicates approval. |
AUTH_RESP_TEXT | Human-readable response text (e.g., "APPROVAL") |
AUTH_GUID | BRIC/token for the transaction. Use for voids, refunds, etc. |
AUTH_CODE | Authorization code from the issuer |
AUTH_AMOUNT | Authorized amount |
AUTH_MASKED_ACCOUNT_NBR | Masked card number for display/receipts |
XML Request Fields
The XML payload is wrapped in a <DETAIL> element. The following fields can be included in your transaction requests:
Required Fields
| Field | Description | Example |
|---|---|---|
TRAN_TYPE | Transaction type code (see Transaction Types) | CCR1 |
AMOUNT | Transaction amount in dollars | 25.99 |
Optional Fields
| Field | Description | Example |
|---|---|---|
TRAN_NBR | Transaction number (auto-incremented if not provided) | 1 |
BATCH_ID | Batch identifier (typically YYYYMMDD format) | 20250108 |
INVOICE_NBR | Invoice or order number for reference | INV-12345 |
TIP_AMT | Tip amount in dollars | 5.00 |
TAX_AMT | Tax amount in dollars | 2.08 |
CLERK_ID | Clerk or employee identifier | EMP001 |
Example: Sale with Optional Fields
Example: Authorization Only (CCR2)
Example: Void (CCRX)
To void a transaction, include the AUTH_GUID (BRIC) from the original transaction:
Example: Refund (CCR9)
Transaction Types
The following transaction types are available. Change the TRAN_TYPE value in your XML message accordingly:
| TRAN_TYPE | Description |
|---|---|
CCR0 | Account Verification |
CCR1 | Retail Purchase Authorization & Capture (Sale) |
CCR2 | Retail Purchase Authorization Only |
CCR7 | Retail Purchase Authorization Reversal |
CCR9 | Retail Return Capture (Refund) |
CCRX | Retail Void |
DB00 | PIN Debit Sale |
DB01 | PIN Debit Return |
DB0V | PIN Debit Reversal |
EB00 | Food Stamp Purchase |
EB01 | EBT Return |
EB02 | Food Stamp Balance Inquiry |
EB05 | EBT Cash Benefits Purchase |
Supported Hardware
The Ingenico SI Cloud API works with any Ingenico Tetra hardware line currently supported:
- Ingenico DESK 2600 (WiFi and non-WiFi)
- Ingenico LANE 3000
- Ingenico LANE 5000
- Ingenico LANE 7000
- Ingenico MOVE 5000
- Ingenico LINK 2500
Visit the Hardware page to order a test terminal.
Support
For further assistance with your integration, please contact our support team or visit the Resources page for additional documentation.