!["SureTap"]("https://archbee-image-uploads.s3.amazonaws.com/QyRay_zUP3KYqO60BLxSV/vBFrA0bCWZyBAFeFBmi24-20260424-153231.gif")
"}
:::
## Sandbox Testing
SureTap is available for testing via our sandbox environment.
### How to set-up the sandbox environment
***File Transfer***
::::WorkflowBlock
:::WorkflowBlockItem
Download the test app [here (.apk)](https://datacapsystems.com/software/SureTap/datacap-sandbox-release-5.2.0.apk) (current version: v5.2.0)
:::
:::WorkflowBlockItem
Connect your Android device via USB. You might have to turn on file transfer when prompted.
:::
:::WorkflowBlockItem
Move the .apk file to the device's download folder.
:::
:::WorkflowBlockItem
On the device, open/run the .apk file.
:::
:::WorkflowBlockItem
Accept the permissions and allow the app to install.
:::
::::
***OR***
***ADB (Android Debug Bridge)***
::::WorkflowBlock
:::WorkflowBlockItem
Download the test app [here (.apk)](https://datacapsystems.com/software/SureTap/datacap-sandbox-release-5.2.0.apk) (current version: v5.2.0)
:::
:::WorkflowBlockItem
Run the command `adb install {path to apk file}`
:::
::::
## Request Access to SureTap SoftPOS API
:::CtaButton{label="Request Access" externalHref="https://dsidevportal.com/request-access" openInNewTab="true"}
:::
:::hint{type="success"}
**Get started:** Request developer credentials for free access to every product's integration guide.
:::
[title] Virtual Gift
[path] Datacap APIs overview/
## What is Virtual Gift?
Virtual Gift API enables merchants to create persistent gift card storefronts. The web pages remain active and can be used by multiple customers over time.
Unlike single-use payment requests, gift card pages are designed to be permanent points of sale for virtual gift cards.
**Key Features**
1. Create branded gift card purchase pages
2. Support multiple payment methods (Credit/Debit, ACH) with Apple Pay and Google Pay support for card payments
3. Three delivery options: Email, SMS, or Print (for hand delivery)
4. Schedule gift card delivery for future dates
5. Customize occasions, amounts, and messaging
6. Embed as widgets/iframes in your own website
7. Receive webhook notifications on purchases
### Virtual Gift Storefront Example
::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/QyRay_zUP3KYqO60BLxSV/Iph-51xXdj_OdII2mSL4_-20260413-204324.png" size="58" width="1900" height="2693" position="flex-start" caption="Virtual Gift page with custom logo and colors" alt="Virtual Gift" darkWidth="1900" darkHeight="2693" showCaption="true"}
### Virtual Gift Card Example
:::Iframe{iframeHeight="0" code="!["Virtual]("https://archbee-image-uploads.s3.amazonaws.com/QyRay_zUP3KYqO60BLxSV/sMD7RaNJH7sIUzBHs7ubU-20260617-195247.png"
)
b. NO\_\_ERROR | | 000002 | ERR\_INVALID\_ATTRIBUTES | | | 000008 | ERR\_CANNOT\_READ\_FILE | | | 000071 | ERR\_END\_OF\_FILE\_REACHED | | | 000072 | ERR\_LOGICAL\_ERROR\_ON\_IO | | | 000073 | ERR\_CANNOT\_SEEK\_FILE | | | 000100 | Card Type Not Accepted | Card type not accepted by processing host. | | 003001 | Transaction or Device Status Error | a. Transaction not found: Cancel attempted while no transaction in process.
b. Tran Device ID XXXXXXXXX is not connected: The DC Direct PIN pad is not connected to Datacap's Cloud server. This typically indicates a network/internet connection issue. | | 003002 | Transaction In Process | a. IN\_PROCESS
b. In Process with Pay Point: A request is already in process. | | 003003 | Socket Error Sending | a. SOCKET\_ERRORSENDING
b. Socket Error sending request. | | 003004 | Socket Already Open | a. SOCKET\_ALREADYOPEN
b. Socket already open or in use. | | 003005 | Socket Creation Failed | a. SOCKET\_CREATEFAILED
b. Could not open IP connection to processor or PIN pad. | | 003006 | Socket Connect Failed | a. SOCKET\_CONNECTFAILED
b. TRANSACTION NOT COMPLETE: Failed to make socket connection with processing host (gateway). | | 003007 | Connection Error | a. SOCKET\_CONNECTIONLOST
b. Login Failed: Timeout waiting for response during login with processing host (Gateway).
c. Socket Connection Lost: Socket connection with processing host lost (gateway). | | 003008 | TCP/IP Initialization Failed | a. TCPIP\_FAILED
b. TCP/IP Failed to Initialize. | | 003010 | Server Timeout | a. TIMEOUT\_ONSERVERRESPONSE
b. TRANSACTION NOT COMPLETE - Timeout Waiting for Server Response: Timeout waiting for gateway response. | | 003011 | SOCKET\_CONNECTCANCELLED | | | 003012 | Crypto Failed | a. CRYPTO\_FAILED
b. 128 bit CryptoAPI failed. | | 003014 | Event Thread Started | a. EVENT\_THREADSTARTED
b. Threaded Auth Started Expect Response Event: Note it is possible the event could fire before the function returns. | | 003016 | DNS\_FAILED | | | 003017 | Event Thread Failed | a. EVENT\_THREADFAILED
b. Failed to start Event Thread. | | 003018 | DNS\_THREADFAILED | | | 003020 | SOCKET\_NOTCONNECTED | | | 003050 | XML Parse Error | a. XML\_PARSEERROR
b. XML Parse Error. | | 003051 | All Connections Failed | a. CONNECTS\_ALLFAILED
b. All Connections Failed. | | 003052 | Server Login Failed | | | 003053 | COINIT\_ERROR | | | 003054 | BAD\_SERVERMSG | | | 003055 | SC550\_ERROR | | | 003066 | PP\_MERCHANTID\_NOMATCH | | | 003067 | PP\_NOTCANADIAN\_TRACK2 | | | 003090 | LOGIN\_FAILED | | | 003091 | ENCRYTION\_ERROR | | | 003100 | SSPI\_INITSECURITYINTERFACE\_FAILED | | | 003101 | SSPI\_ACQUIRECREDENTIALSHANDLE\_FAILED | | | 003102 | SSPI\_INITIALIZESECURITYCONTEXT\_FAILED | | | 003103 | SSPI\_SOCKETBASED\_FAILURE | | | 003104 | SSPI\_QUERYATTRIBUTES\_FAILURE | | | 003105 | SSPI\_OUTOFMEMORY\_FAILURE | | | 003106 | SSPI\_CONTROLTOKENAPPLICATION\_FAILURE | | | 003107 | SSPI\_MESSAGETOOLARGE\_FAILURE | | | 003108 | SSPI\_CERT\_CN\_NOMATCH | | | 003109 | SSPI\_CERT\_ISSUER\_NOMATCH | | | 003110 | SSPI\_CERTGETCERTIFICATE\_CHAIN\_FAILURE | | | 003120 | SSPI\_CERT\_E\_EXPIRED | | | 003128 | SSPI\_CERT\_E\_UNTRUSTEDROOT | | | 003136 | SSPI\_CERT\_E\_UNKNOWN | | | 003137 | SSPI\_CERT\_DNS\_NOMATCH | | | 003138 | SSPI\_QUERYATTRIBUTES\_REMOTE\_CERT\_CONTEXT | | | 003201 | LOST\_DATATRAN\_CONNECTED\_SIGNAL | | | 003288 | ERROR\_UNKNOWN | | | 003301 | MPT\_NOMATCHINGTRACEDATA | | | 003317 | Processing Thread Failed | a. PROCESSING\_THREADFAILED
b. dsiEMVAndroid internal error starting transaction thread. | | 003318 | 128 bit CryptoAPI Failed | Requires IE5(or higher) with High Encryption Pack. Failed to create encrypted session. Ensure proper encryption libraries are present on computer. | | 003325 | XML Document Error | a. ERROR\_3325: XML parse errors.
b. TRANSACTION NOT COMPLETE - Purchase Not Found in XML Document: \
b. Invalid Amount: Amount validation failure.
c. Credit Required and Not Presented: Requested \
d. Debit not supported for \{TranCode}: Debit AID selected and TranCode is something other than EMVSale or EMVReturn.
e. Debit Required and Not Presented: Requested \
f. Cash Back NOT Supported on this Transaction Type: \
g. Gratuity NOT Supported on this Transaction Type: \
h. Total Amount cannot be zero: Sum of \
i. Invalid Tran Code: \
j. IP Pad Must be encrypted: Datacap requires all devices communicating over IP to be encrypted.
k. Communication Method (IP) is Not Supported: SecureDevice value does not support IP communication method. | | 003327 | ERROR\_3327 | comport/connection failure, device not found | | 003328 | Transaction Not Complete or Pinpad Response Error | a. ERROR\_3328: pinpad response errors, ICC status errors, explicit data trancode not supported, NAK.
b. Account Not Entered: Request is cancelled on device during manual entry.
c. Amount Not Acknowledged: Request is cancelled on device during amount confirmation.
d. Cancelled at POS: Transaction successfully cancelled by POS using TransactionCancel request.
e. Card Blocked: EMV card blocked.
f. Card Removed: Card removed prematurely during EMV transaction.
g. Cash Back Not Allowed: \
h. Encryption Failed: Device is configred for E2E and card data should have been encrypted but encryption failed.
i. MSD Contactless Not Supported: The presented card would have resulted in an MSD contactless transaction which is no longer allowed.
j. No DUKPT key: PIN entry required but no key isn't injected in the expect slot.
k. No Signature Data: Signature prompt is confirmed without signature data to return.
l. Paper Jam: Printer detected paper jam.
m. Paper Out: Printer detected out of paper.
n. This Device Does Not Support PrintReceipt: Device does not have a printer.
o. This Device Does Not Support Signature: GetSignature TranCode attempted when device model does not support signature capture.
p. Card Not Removed: Card not removed during EMVPadReset.
q. Error: General error (default case).
r. Timeout Waiting for PinPad: Timed out waiting for user. | | 003329 | ERROR\_3329 | NETePay response error, "Invalid CmdStatus from NETePay" is probably the only one, could also be fallback not allowed on amex, major credit card not allowed | | 003330 | Invalid Card or Device Data | a. ERROR\_3330: error retrieving serial number from device, or field length data incorrect (min/max PAN).
b. GetPrePaidStripe - Card not whitelisted.
c. Preamble not satisfied: GetPrePaidStripe - Leading characters do not match \
d. Max Len Exceeded: GetPrePaidStripe - Card exceeds \
e. Min Len not satisfied: GetPrePaidStripe - Card is shorter than \
b. TRANSACTION CANCELLED: Request is cancelled on device during any process which is not explicitly handles by another error. | | 003350 | Host Response Timeout | a. ERROR\_TIMEOUT\_ONHOSTRESPONSE
b. Timeout Waiting for Host Response: No response from processing host. | | 003360 | PROCTRANIFCHIP | | | 003390 | ERROR\_3390\_USBHID | | | 003397 | ERROR\_3397\_VIVOVEND3 | | | 003402 | PARM\_PARSE\_ERROR | | | 003403 | COMPACT\_FLASH\_ERROR | | | 003404 | CHALLENGE\_RESPONSE\_ERROR | | | 003405 | PARM\_ERRFROMSERVER\_ERROR | | | 003600 | GENERIC\_DNS\_ERROR | | | 003650 | GENERIC\_SOCKET\_ERROR | | | 010004 | WSAEINTR | EINTR | | 010013 | WSAEACCES | EACCES | | 010014 | WSAEFAULT | EFAULT | | 010022 | WSAEINVAL | EAI\_BADFLAGS | | 010035 | WSAEWOULDBLOCK | EWOULDBLOCK | | 010036 | WSAEINPROGRESS | EINPROGRESS | | 010037 | WSAEALREADY | EALREADY | | 010038 | WSAENOTSOCK | ENOTSOCK | | 010040 | WSAEMSGSIZE | EMSGSIZE | | 010045 | WSAEOPNOTSUPP | EOPNOTSUPP | | 010047 | WSAEAFNOSUPPORT | EAI\_FAMILY | | 010048 | WSAEADDRINUSE | EADDRINUSE | | 010050 | WSAENETDOWN | ENETDOWN | | 010052 | WSAENETRESET | ENETRESET | | 010053 | WSAECONNABORTED | ECONNABORTED | | 010054 | WSAECONNRESET | ECONNRESET | | 010055 | WSAENOBUFS | ENOBUFS | | 010056 | WSAEISCONN | EISCONN | | 010057 | WSAENOTCONN | ENOTCONN | | 010058 | WSAESHUTDOWN | ESHUTDOWN | | 010060 | WSAETIMEDOUT | ETIMEDOUT | | 010061 | WSAECONNREFUSED | ECONNREFUSED | | 010065 | WSAEHOSTUNREACH | EHOSTUNREACH | | 011001 | WSAHOST\_NOT\_FOUND | EAI\_NONAME | | 011004 | WSANO\_DATA | EAI\_NODATA | | 099098 | Invalid Request - Failed to Parse Request. | Unable to parse POS request | ## Store and Forward Error Codes | **DSIXReturnCode** | **TextResponse** | **Description** | | ------------------ | --------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 100 | Card Type Not Accepted | Card type not accepted by processing host. | | 5000 | General Error | a. Failed to encrypt.
b. Failed to decrypt.
c. Forwarding error: The number of requests is zero, but there are # requests in the request container.
d. Forwarding error: The dollar total is zero, but there are # requests in the request container.
e. No requests to forward.
f. A request identifier was not found. Note: request id is RecordNo or RefNo.
g. Invalid status for request id. A forwarded status can only be eApproved, ePartiallyApproved, eDeclined, eSuccess, or eError. Note: request id is RecordNo or RefNo.
h. Failed to insert request id into request container. Note: request id is RecordNo or RefNo.
i. Cannot remove request id from request container because it cannot be found. Note: request id is RecordNo or RefNo.
j. No requests to forward.
k. This request's "AuthCode" is "OFFLIN", but the original request id cannot be found. Note: request id is RecordNo or RefNo. Could find an existing "parent" transaction for an OFFLIN child transaction.
l. # row(s) should have been updated, # were updated.
m. Encryption password required.
n. Database version number required.
o. New transactions cannot use StoreAndForward "RecordNo".
p. Using StoreAndForward's AuthCode of "OFFLIN" and a RecordNo/RefNo is not supported for TranCodes of "#". Note: RecordNo or RefNo, not both. Store and Forward AuthCode and request identifier not supported for TranCode used.
q. The sum of pending non-child adjustments (#), orphaned child adjustments (#), and non-child voids (#) should not be greater than the stored pending transaction count (#).
r. Cannot store “OFFLIN” AuthCode transactions while a "SAF\_ForwardAll” is in progress.
s. Unknown Error. | | 5001 | Failed to initialize SAF Error | a. Function "Open" must be called first.
b. Failed to initialize StoreAndForward. | | 5002 | Database Error | a. Purchase must be greater than zero.
b. Purchase must be greater than zero for request id. Note: request id is RecordNo or RefNo.
c. Not connected to the database.
d. Result columns should be #, # were found.
e. Duplicate request id found in request container while loading from database. Note: request id is RecordNo or RefNo.
f. Cannot find "Purchase" for request id while loading from database. Note: request id is RecordNo or RefNo.
g. Duplicate request id found in request container after insert into database. Note: request id is RecordNo or RefNo.
h. Insert failed.
i. Only one row should have been inserted, # were inserted.
j. Database update failed.
k. Only one row should have been updated, # were updated.
l. Unexpected database version, expecting #, found #. Note: NETePay was asked to open an older database.
m. Database table does not exist.
n. Database table does not have the correct schema.
o. Database tables "STORE\_AND\_FORWARD" and "STORE\_AND\_FORWARD\_DETAIL" do not exist.
p. Cannot find the database version information.
q. DATABASE: Note: Error thrown by underlying database.
r. Unknown Error. | | 5003 | Validation Error | a. OfflineTransactionPurchaseLimit is required.
b. MaxTransactions is required.
c. Unreasonable maximum transactions (too low?). Note: validation functionality that is controlled by a flag from NETePay, default is off.
d. Unreasonable maximum transactions (too high?). Note: validation functionality that is controlled by a flag from NETePay, default is off.
e. Unreasonable transaction limit value (too low?). Note: validation functionality that is controlled by a flag from NETePay, default is off.
f. Unreasonable transaction limit value (too high?). Note: validation functionality that is controlled by a flag from NETePay, default is off.
g. Transaction would exceed maximum transactions. Note: validation functionality that is controlled by a flag from NETePay, default is off.
h. Purchase amount is greater than the purchase limit. Note: validation functionality that is controlled by a flag from NETePay, default is off.
i. Purchase amount is less than the purchase minimum. Note: validation functionality that is controlled by a flag from NETePay, default is off.
j. Don't allow any forwarding if there are PreAuths. Note: validation functionality that is controlled by a flag from NETePay, default is off.
k. "RecordNo" is required.
l. "RefNo" is required.
m. "RecordNo" is not numeric.
n. "RefNo " is not numeric.
o. The initial transaction was not a "Sale" transaction, it was a .
p. The initial transaction was not a “Return" transaction, it was a .
q. Transaction previously voided.
r. "RecordNo" is not in the correct format. It should be 12 characters long, starting with "SAF:" and the remaining characters being numeric.
s. Transactions cannot be stored. There are stored transactions that are older than # hour(s) and must be forwarded. | | 5004 | Invalid Request Error | a. Request cannot be empty. | | 5005 | No Requests to Forward Error | | | 5006 | Cannot Find RequestId Error | a. Cannot find request id while forwarding. Note: request id is RecordNo or RefNo. | | 5100 | Forward In Progress Error | | | 5101 | Failed to Start Forward All Error | | | 5102 | Not Enabled Error | | | 5103 | Timeout | | | 5104 | Auth Error | | | 5105 | TranCode Abort | | | 5106 | Interface Error | | ## Contact Datacap Support Contact Datacap Support for assistance with error codes [space] Dual Multi-Pricing (/dual-multi-pricing) [title] Dual/Multi-Pricing [path] / ## Choose an interface: ::::LinkArray{contentSource="CUSTOM" customOrder="NmkjAuxbagp8uKS3bXbSb,e3LfN7SdRWajmWAf61qxl,YgWvc1AGvSVOwy6wO6lia"} :::LinkArrayItem DC Direct™ *Direct to PIN pad integration without local hardware or software* [DC Direct](docId\:bgS3qQ7pE4ePLwDT_mZaH) ::: :::LinkArrayItem dsiEMVAndroid™ *Semi-integrated payments integration for Android Point of Sale applications.* [dsiEMVAndroid](docId\:MDRDGlvvD0op2XKCc_Ozg) ::: :::LinkArrayItem dsiEMVApple™ *Semi-integrated payments integration for Apple Point of Sale applications* [dsiEMVApple](docId\:smQte-SLWSl2TJgLGJu5X) ::: :::LinkArrayItem dsiEMVUS® *US EMV semi-integrated payments integration for PC-based Point of Sale systems* ** [dsiEMVUS](docId\:iCQcuWcpH7ZtqFB9ar8Sh) ::: :::: [title] Home [path] / [space] Point of Sale Developer FAQ (/point-of-sale-developer-faq) [title] Glossary Terms [path] / This glossary defines the payment and point-of-sale (POS) terms used in Datacap's developer documentation, (terms like EMV, PCI DSS, tokenization, point-to-point encryption (P2PE), 3D Secure, ACH, card-present and card-not-present processing, etc). It is written for POS developers, ISVs, and integrators. The first table covers Datacap-specific products/terms, and the second covers general payments industry terms, with links to primary sources such as PCI SSC, EMVCo, Nacha, and NIST at the bottom of the page. ## Datacap Products | **Product** | **Description** | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | NETePay Hosted™ | Datacap's Omnichannel payments gateway | | NETePay™ | Datacap's flagship payments integration platform providing Windows POS applications with integrated credit, debit, eWIC/EBT, FSA, and gift/loyalty processing to virtually all payment processors in North America via one standardized interface. NETePay uses the dsiEMVUS® and dsiPDCX® ActiveX controls. | | Datacap Gift™ | Datacap's omnichannel gift card platform enabling card-present and card-not-present gift card transactions. Supports real-time reporting, white-label branding, multi-location management, and pre-loaded promotions. | | Pay API™ | RESTful payment API for eCommerce credit, debit, and gift transactions using standard HTTP methods, content types, and resource-oriented architecture. | | DC Direct™ | Embeds payment logic directly into payment devices, communicating directly with NETePay Hosted. No additional Datacap hardware or software required. Available in stand-alone and semi-integrated mode. | | SureTap™ | SoftPOS solution that enables SMB retailers to accept contactless payments directly on mobile devices without additional hardware, reducing deployment costs and simplifying merchant onboarding. | | dsiEMVUS® | Windows ActiveX control for EMV chip card transaction processing in a multi-tiered client-server architecture. Communicates with in-store NETePay servers using IP. Controls approved EMV PIN pads via RS232, USB, or IP. | | dsiEMVAndroid™ | Android .aar library for EMV transaction processing. Communicates exclusively with NETePay Hosted. Controls approved EMV devices over Bluetooth LE, USB, and IP. Minimum API level 23. | | dsiEMVApple™ | Apple framework for EMV transaction processing on iOS devices. Communicates exclusively with NETePay Hosted. Controls approved EMV devices over Bluetooth LE or IP. | | Virtual Gift | Gift card processing for card-not-present environments, enabling digital gift card sales, loads, and balance inquiries without a physical card. | | Payment Links | Empowers partners to deliver a fully branded webpages for merchants to share via text or email. Supports configurable payment types, tips, and surcharges. Payment Links can only be used once. | | Hosted Payments Pages | Secure hosted payment pages for web-based checkout. Supports redirect links, QR codes, and embedded iframe widgets. Handles credit, debit, ACH, and gift card payments with customizable branding and real-time webhook notifications. | | PayLoader™ | Multi-OEM Terminal Management System (TMS) for remote configuration, deployment, and management of payment device fleets across one or thousands of locations. | | PSCS™ | Product and Software Configuration System. Datacap's product portal for automatic software updates and configuration management. | | GIFTePay™ | Payments integration that provides Windows POS applications with integrated gift/loyalty processing to virtually all gift card processors in North America via one standardized interface. GIFTePay primarily uses the the dsiPDCX® ActiveX control. | ## Industry-specific and developer jargon | Term | Definition | | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 3D Secure (3DS) | A cardholder-authentication protocol for online card payments. The issuer verifies the shopper during checkout, which can shift fraud-chargeback liability away from the merchant. \[1] | | 3D Secure 2 (3DS2) | The EMVCo-specified successor to the original 3D Secure. It passes richer transaction data to the issuer and supports flexible authentication methods, so more payments can be approved without an extra challenge step. \[1] | | ACH | Automated Clearing House: the US electronic network that moves direct deposits and direct payments between bank accounts for consumers, businesses and governments, without cards, wires, checks or cash. \[2] | | AES-CBC | A mode of the AES block cipher in which each plaintext block is combined with the previous ciphertext block before encryption, so identical plaintext blocks produce different ciphertext. Specified in NIST SP 800-38A. \[3] | | AES-ECB | The simplest AES mode: each block is encrypted independently with the same key, so identical plaintext blocks yield identical ciphertext. Specified in NIST SP 800-38A and generally unsuited to data with repeating patterns. \[3] | | AFT | Account Funding Transaction: a card transaction that moves money from a cardholder's account to fund another account, such as a wallet, rather than purchasing goods. | | AI model | A software system trained on data to learn patterns, then used to make predictions, classify inputs or generate content. | | asynchronous | Describes operations that don't happen in lockstep: one system starts a request and carries on, and the result arrives later on its own timeline. | | authentication rate | The share of card payments for which 3D Secure authentication was attempted, out of all card payments. | | authentication success rate | The share of 3D Secure authentication attempts that succeeded. | | authorized person | An individual with significant responsibility to control, manage or direct a business, such as an executive officer or senior manager. Often used as the 'control person' in onboarding and KYC. \[4] | | authorization rate | The percentage of attempted card payments that issuers approve. | | Address verification system (AVS) | A fraud check that compares the billing address a customer gives with the address on file at the card issuer; the issuer returns a match code to the merchant. | | beneficial owner | An individual who directly or indirectly owns 25% or more of a legal entity. Under FinCEN's CDD Rule, one person with significant control is also identified. \[4] | | billing period | How often invoices are generated and sent to customers, independent of the service period. | | buy now, pay later (BNPL) | Short-term financing that lets a customer take a purchase now and pay in installments, commonly four or fewer and often interest-free. \[5] | | capture (a charge) | Collecting funds that were previously authorized. Authorization places a hold on the cardholder's available credit; capture requests that the money actually be transferred, often later in settlement. | | automatic capture | Funds are captured as soon as a charge is authorized, with no separate step. | | manual capture | Funds are captured in a separate step after authorization, for example once an order ships. | | card authentication | A step where the issuer verifies the cardholder before approving a payment, such as a one-time code sent to the cardholder's phone. \[1] | | card issuer | The institution that issues a payment card to a cardholder, usually a bank, or the card network itself in the case of American Express. | | card network costs | Fees charged by card networks, principally interchange and scheme (assessment) fees. | | card networks | Organizations such as Visa, Mastercard, American Express and Discover that operate the infrastructure and rules for card transactions between merchants' and cardholders' banks. | | card-not-present | A transaction in which the physical card is not read by the merchant, such as online, phone or mail orders, and card-on-file or recurring payments. | | card token | A surrogate value that replaces the cardholder's primary account number (PAN) so the real number isn't stored or transmitted. \[6] | | charge card | A card that requires the full balance to be paid at the end of each billing cycle, rather than allowing a revolving balance. | | chargeback | A reversal initiated by a cardholder's bank after the cardholder disputes a transaction; the disputed funds are debited from the merchant until the dispute is resolved. | | Content Security Policy | A browser security feature in which a site sends instructions telling the browser what its code may do. It helps mitigate attacks such as cross-site scripting (XSS) and data injection. \[7] | | Card verification code check (CVC) | The 3- or 4-digit security code on a card (CVC, CVV or CID depending on the brand), used in card-not-present transactions to help confirm the cardholder has the physical card. | | deprecated | Technology that is no longer recommended and may stop working after an announced date. | | digital wallet | An app or service that stores payment credentials and lets customers pay from a phone or other smart device, often by contactless tap. | | Electronic Commerce Indicator (ECI) | A code returned with a 3D Secure authentication result that shows how and whether the cardholder was authenticated; it is used to determine liability shift eligibility. | | EMV | The global specifications for chip-card and contactless acceptance, originally developed by Europay, Mastercard and Visa and now managed by EMVCo. | | EMVParamDownload | A Datacap command that loads parameters from the active deployment onto the PIN pad so it can run EMV transactions. Required for new installs and whenever deployment parameters change. \[8] | | FDIC | The Federal Deposit Insurance Corporation: a US agency that insures deposits, supervises banks and resolves failures to maintain stability and public confidence in the financial system. \[9] | | fixed and variable portion | The two parts of a fee. For a rate of 2.04% + $0.10, 2.04% of the amount is the variable portion and $0.10 per transaction is the fixed portion. | | FSA/HSA | Debit cards tied to Flexible Spending or Health Savings Accounts, funded with pre-tax dollars and limited to eligible medical purchases at qualifying merchants. | | fulfillment | Delivering the goods or services a customer purchased, typically after payment is collected. | | gross sales | Total sales over a period before returns, discounts or deductions. | | GST | Goods and services tax: a consumption tax charged on most goods and services. In Canada the federal GST is 5%, collected by sellers and remitted to the government. \[10] | | HST | Harmonized Sales Tax: in certain Canadian provinces, a single tax that combines the federal GST and the provincial sales tax. \[10] | | interchange fee | A fee paid by the merchant's bank (acquirer) to the cardholder's bank (issuer) on card transactions. For US debit cards, the Federal Reserve's Regulation II caps what issuers can receive. \[11] | | know your customer | KYC: the procedures businesses use to verify a customer's identity and assess risk. It is part of anti-money-laundering (AML) compliance, including FinCEN's Customer Due Diligence Rule. \[4] | | legacy | Technology that remains in service but is no longer recommended for new development. | | liability shift | When a transaction is authenticated through 3D Secure, responsibility for certain fraud chargebacks can move from the merchant to the card issuer. \[1] | | mandate | The customer's written authorization to debit their bank account, obtained before the first ACH debit. | | marketplace | A platform that hosts storefronts or listings for multiple sellers under the platform's own brand. | | MCC | Merchant Category Code: a four-digit code that classifies the type of goods or services a merchant provides. | | Merchant ID | A unique identifier assigned to a merchant by its processor or acquirer, used to identify the merchant during processing and settlement. | | NACHA | Nacha: the organization that establishes and oversees the rules governing the ACH Network. \[2] | | NSF | Non-sufficient funds: the reason an ACH debit is returned when the account lacks funds, reported with return code R01. | | Offline PIN | A PIN verification method for chip cards in which the PIN is checked by the card itself, without contacting the issuer. | | Online PIN | A PIN verification method in which the PIN is encrypted and sent to the issuer for verification during authorization. | | on-session payment | A payment made while the customer is actively present in the checkout flow and able to authenticate. | | partial refund | A refund for less than the full remaining refundable amount of a transaction. | | payment rails | The financial networks and infrastructure that move money from payer to payee, such as card networks, ACH and wire. | | payout | A transfer of funds to an external account, usually a bank deposit. | | PCI compliance | Adherence to the PCI Data Security Standard, which applies to entities that store, process or transmit cardholder data or could affect the security of the cardholder data environment. \[12] | | Personally identifiable information | Information that can identify an individual, alone or combined with other data, such as name, Social Security number, biometric records, or linked financial and employment details. \[13] | | PST | Provincial Sales Tax: a retail sales tax charged by some Canadian provinces on consumer purchases, separate from the federal GST. | | QST | Québec Sales Tax: Quebec's provincial sales tax, collected alongside the GST on most property and services sold in the province. \[10] | | Quick Chip EMV | A US contact-chip flow that lets the cardholder remove the card before the authorization response returns. The terminal completes the chip transaction as a deferred authorization. \[14] | | retail sales | For tax purposes, sales to end consumers, excluding goods bought for resale. | | reversal | Cancellation of a transaction before it settles. | | RST | Retail Sales Tax: a Manitoba tax on the retail sale or rental of most goods and certain services, charged at 7% and calculated before GST. \[15] | | service interval | The period used to measure usage and apply pricing, independent of billing cadence. | | settle | Funds from authorized and captured transactions are transferred to the merchant's account. | | Standard EMV | A contact EMV flow in which the card stays in the reader through online authorization; the transaction completes after the chip validates the issuer response with a second cryptogram, and is reversed if validation fails. | | stored-value account | An account that holds funds, typically loaded from an external bank account. | | tax code | A category assigned to a product or service that determines how it is taxed. | | TLS | Transport Layer Security: the protocol that secures data in transit between a client and server by providing authentication, confidentiality and integrity. It succeeded SSL. \[16] | | Track 2 | Magnetic-stripe data format holding the card number (PAN), expiration date and issuer-defined data, used for in-person processing. | | 2FA | Two-factor authentication: a security process that requires two different authentication factors, such as a password and a one-time code, to verify identity. | | VAT | Value-added tax: a consumption tax charged at each stage of production and distribution, ultimately borne by the end consumer. | | webhook | An automated HTTPS message sent from one system to another when an event occurs, usually carrying a JSON payload. | | wire transfer | An electronic transfer of funds from one party's bank account to another's, also called a bank or credit transfer. | | Convenience Fee | A fee charged for offering an additional or expedited payment channel, such as online or phone payments. It differs from a surcharge because it pays for the convenience, not for card-processing costs. | | Payment Fee | A non-cash adjustment that lets merchants add a fee to an electronic payment. Part of Datacap's Payment Fee Suite, which covers surcharge with lookup, dual/multi-pricing, split fee funding and convenience fees. The fee and description appear on the receipt. | | Dual/Multi-Pricing | Showing different prices for the same item depending on payment method, such as a lower cash price (cash discounting). Works best in-person where a device can display each price. | | Surcharge | A fee a merchant adds to a card transaction to offset processing costs. Regulated by card networks and many states. | | Omnichannel Payments | Payment acceptance that unifies online, mobile and in-store channels so customers and merchants get one consistent experience and view of payment data. | | Tokenization | Replacing sensitive payment data, such as the PAN, with a surrogate token that has no exploitable value outside the issuing payment system. \[6] | | Point-to-Point Encryption (P2PE) | Encryption that protects card data from the point of capture to the secure decryption environment, leaving it unreadable in between. PCI SSC lists validated P2PE solutions that reduce merchant PCI scope. \[17] | | Near Field Communication (NFC) | A short-range wireless technology (a few centimeters) behind tap-to-pay, used in contactless cards and mobile wallets such as Apple Pay and Google Pay. \[18] | | Batch Processing | Collecting transactions over a period, often a day, and submitting them together for settlement rather than one at a time. | | Payment Gateway | Technology that relays transaction data between merchants and processors or card networks for authorization and settlement. | | Independent Sales Organization (ISO) | A third party that partners with acquirers or processors to sell and support merchant accounts and payment services. | | Hosted Payment Page (HPP) | A payment page hosted by a gateway or processor where customers enter card data, keeping the data off the merchant's own site and reducing PCI scope. | | PIN Pad | A device that securely captures the cardholder's PIN and typically also reads chip and contactless cards. See also: | | Acquiring Bank | A financial institution that processes card transactions for a merchant, maintains its merchant account and settles funds from issuers. | | Payment Processor | A company that routes and processes transactions between merchants, card networks and banks, handling authorization, clearing and settlement. | ## Sources 1. [EMVCo, EMV 3DS for E-Commerce quick resource](https://www.emvco.com/wp-content/uploads/2022/09/Quick-Resource_-EMV-3DS-for-E-Commerce.pdf) 2. [Nacha, What is ACH?](https://www.nacha.org/what-ach) 3. [NIST, Block Cipher Techniques (SP 800-38A modes)](https://csrc.nist.gov/projects/block-cipher-techniques/bcm) 4. [FinCEN, CDD Rule FAQs](https://www.fincen.gov/resources/statutes-and-regulations/cdd-rule-faqs) 5. [CFPB, Consumer use of BNPL and other unsecured debt](https://www.consumerfinance.gov/data-research/research-reports/consumer-use-of-buy-now-pay-later-and-other-unsecured-debt/) 6. [PCI SSC, Tokenization Guidelines](https://listings.pcisecuritystandards.org/documents/Tokenization_Guidelines_Info_Supplement.pdf) 7. [MDN Web Docs, Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) 8. [Datacap Support, EMV Parameter Download](https://datacapsystems.com/support-articles/emv-parameter-download) 9. [FDIC, What We Do](https://www.fdic.gov/about/what-we-do/) 10. [Revenu Québec, GST/HST and QST](https://www.revenuquebec.ca/en/businesses/consumption-taxes/gsthst-and-qst/) 11. [Federal Reserve, Regulation II](https://www.federalreserve.gov/paymentsystems/regii-about.htm) 12. [PCI SSC, PCI Data Security Standard](https://www.pcisecuritystandards.org/standards/pci-dss/) 13. [NIST SP 800-122](https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-122.pdf) 14. [Visa, Quick Chip for EMV specification v2.0](https://usa.visa.com/content/dam/VCOM/regional/na/us/run-your-business/documents/quick-chip-emv-specification.pdf) 15. [Manitoba Finance, Retail Sales Tax](https://www.gov.mb.ca/finance/taxation/taxes/retail.html) 16. [IETF, RFC 8446 (TLS 1.3)](https://datatracker.ietf.org/doc/html/rfc8446) 17. [PCI SSC, Point-to-Point Encryption](https://www.pcisecuritystandards.org/standards/point-to-point-encryption-p2pe/) 18. [NFC Forum, What NFC does](https://nfc-forum.org/learn/what-nfc-does) [title] Payment Integration FAQ for POS Developers [path] / Common questions from software developers adding card payments to point-of-sale, kiosk, and unattended applications, answered by [Datacap Systems](https://datacapsystems.com), a payments solutions provider for POS software companies since 1983. This page covers architecture, device and processor compatibility, PCI scope, and platform capabilities. Full technical reference material like transaction definitions, request and response schemas, sample code, and certification guides lives in the Datacap [Dev Porta](https://dsidevportal.com/)[l](https://dsidevportal.com/), which is free to access with approved developer credentials. *** ::::ExpandableHeading # How do I add payment processing to my point-of-sale software? There are three broad approaches. You can integrate directly to a payment processor, which means a separate certification and codebase for every processor you want to support. You can embed a single processor's SDK, which ties your product to that processor and its merchant pricing. Or you can integrate once to a payments middleware layer that abstracts the processor and the terminal behind one interface. The middleware approach is what most established POS ISVs choose, because merchant demand for a specific processor is the thing you cannot control. Datacap provides that layer: one integration to your application, then processor and device selection becomes a deployment-time configuration rather than a development project. Before you write code, scope which markets you serve: retail, restaurant, QSR/Fast-Casual, parking, lodging/hospitality, healthcare, grocery, unattended, ecommerce, entertainment, etc. and consider the architecture of your point of sale. :::hint{type="success"} **Get started:** Compare integration paths in the [Datacap Dev Portal](https://www.dsidevportal.com/): request developer credentials for free access to every product's integration guide. ::: :::: *** ::::ExpandableHeading # What's the best payment middleware for a POS ISV in the US? There is no single answer, but there is a checklist worth applying. Evaluate any payments gateway or middleware layer against: - [ ] How many payment processors are supported - [ ] How many models it supports across manufacturers and payment processors - [ ] Whether it keeps your Point of Sale application out of PCI scope - [ ] Whether it supports card-present and card-not-present through one integration - [ ] What types of tokens are support (processor-agnostic gateway tokens, Network tokens, etc.) - [ ] How are processor certifications handled (ideally the vendor holds the processor certifications so you do not have to) - [ ] Can you deploy out-of-the-box processing via standalone solutions that can be configured to semi-integrated mode once development is complete Datacap was built specifically for these use-cases: US and Canadian POS software companies, so they can support Point of Sale developer's merchants via a semi-integrated or standalone. That focus shows up in breadth of processor and device support and in semi-integrated architectures that keep cardholder data out of the POS application entirely. :::hint{type="success"} **Get started:** Review the [supported processors list](https://datacapsystems.com/supported-features-processors) and [compatible devices](https://datacapsystems.com/compatible-devices), then request Dev Portal access to see the integration surface for yourself. ::: :::: *** ::::ExpandableHeading # How can a POS provider support multiple payment processors with one integration? You use an abstraction layer. Your application sends a normalized transaction request to a payment middleware component; the middleware translates that request into each processor's message format, manages the processor connection, and returns a normalized response. Your code path does not change when the processor changes. In Datacap's architecture, the POS application integrates to a client component — a Windows control, a mobile library, or a REST API depending on platform — which communicates with a Datacap payment server. Processor selection happens in the merchant's deployment configuration, not in your source code. Datacap holds the processor certifications, so adding a processor to your supported list does not require a new development or certification cycle on your side. That is the difference between supporting fifteen processors and certifying to fifteen processors. :::hint{type="success"} **Get started:** See how processor abstraction works across [NETePay Hosted](https://archbee.dsidevportal.com/pscs-api/netepay-hosted) in the Dev Portal, or browse [Datacap's solution overview](https://datacapsystems.com/solutions). ::: :::: *** ::::ExpandableHeading # Which payment terminals work with Chase, TSYS, Fiserv, Global Payments, Heartland, Worldpay or Elavon? Terminal () compatibility is set by the combination of device model, payment processor, and the integration method in between; not by the terminal manufacturer alone. A given may be supported on one processor and not another, and encryption options such as standard versus PCI-validated P2PE vary by pairing. Datacap maintains support across [PAX](https://www.pax.us/), [Ingenico](https://ingenico.com/us-en), [Verifone](https://www.verifone.com/en-us), [ID TECH](https://idtechproducts.com/), [Touch Dynamic](https://www.touchdynamic.com/), and additional kiosk and tablet , mapped against North American processors including TSYS, Global Payments, Elavon, Heartland, Worldpay, Fiserv/First Data Rapid Connect, Chase, EVO, Moneris, and others. Because Datacap holds the certifications for these pairings, the authoritative device-by-processor matrix is published and kept current rather than assembled from separate processor and manufacturer documentation. :::hint{type="success"} **Get started:** Filter the live [compatible devices matrix](https://datacapsystems.com/compatible-devices) by Datacap solution and/or manufacturer, and check the [supported processors list](https://datacapsystems.com/supported-features-processors). ::: **** :::: **** *** ::::ExpandableHeading # What is a semi-integrated payment solution and who provides one? In a semi-integrated model, the Point of Sale (POS) application never touches cardholder data. The POS sends a transaction request including the amount, transaction type, reference information, etc to a or payment component, which then prompts the customer, captures and encrypts the card data, routes it to the payment processor through the payment gateway, and returns a response to the POS, along with a token when one is requested. Sensitive card data flows around the POS, not through it. What semi-integration removes is the POS's handling of cardholder data, not its control of the checkout experience. The POS still sets the amount and flow and composes its own prompt sequence from non-payment . Semi-integrated architectures are offered by payment gateway and middleware providers. Datacap provides them for Windows, Android, iOS, Linux, and cloud-based POS systems. :::hint{type="success"} **Get started:** Explore [Datacap's payment solutions](https://datacapsystems.com/solutions). ::: :::: *** ::::ExpandableHeading # How do I make my Point of Sale (POS) PCI compliant without handling card data? The most reliable route is to design the application so it never receives cardholder data in the first place. If a payment component takes direct control of the card-entry device (MSR, PIN pad, contactless reader, or EMV terminal) and captures the account number, expiration date, CVV, and PIN outside your application, your POS software can generally be kept out of PCI scope. Two design details matter as much as the architecture. First, when a device cannot read a card, manual entry should be handled in a window controlled by the payment component, not by a POS screen. Second, the client component should store nothing locally: transaction storage, logging, and data management belong on the payment server. Datacap's client components are built on exactly this model, with options for PCI-validated P2PE available on selected devices. :::hint{type="success"} **Get started:** [Request developer credentials](https://dsidevportal.com/request-access) for free access to every Datacap product's integration guide. ::: :::: *** ::::ExpandableHeading # What's the best way to add EMV chip card support to a Windows POS application? For a Windows POS, the practical path is a client-server design: a client component installed alongside your application on the workstation, communicating with an EMV-certified payment server. The client component takes direct control of an approved EMV , over a serial or USB virtual COM port, or over IP and manages the full EMV interaction, including the card-present prompts, kernel behavior, and encryption. Your application sends a transaction request and receives a result. This matters because EMV certification is the expensive part. Certifying an EMV kernel and terminal application per device and per processor is a substantial, recurring effort. Using a component that sits in front of already-certified server and device combinations removes that work from your roadmap. Datacap provides Windows components for both EMV and broader multi-tender processing, with automatic failover across redundant payment servers for high availability. :::hint{type="success"} **Get started:** Review the [dsiEMVX (dsiEMVUS)](https://archbee.dsidevportal.com/dsiemvus) integration guides in the Dev Portal. ::: :::: *** ::::ExpandableHeading # Who provides white-label payment gateway technology for software companies? White-label gateway technology lets a software company or Independent Sales Organization (ISO) present payments as part of its own product rather than sending merchants to a third-party brand. What varies between providers is how much is actually brandable and how much gateway work you inherit. Datacap's white-labeled gateway () covers login and welcome screens, custom URLs, reporting dashboards, payment forms, device overlays and welcome screens, gift card platforms, payment links, and logos and colors. The stated value is brand ownership plus speed to market (going live without building a gateway or pursuing processor certifications yourself). For a POS ISV, that means merchants see your brand from checkout through reporting, while processor connectivity, certification maintenance, and device support stay with Datacap. :::hint{type="success"} **Get started:** See Datacap's [white-labeled gateway overview](https://datacapsystems.com/white-labeled-solutions) ::: **** :::: *** ::::ExpandableHeading # What does Datacap Systems do? [Datacap Systems](https://datacapsystems.com/) (Datacap) is a payments gateway and payments middleware platform for point-of-sale software companies. Founded in 1983 in Montgomeryville, Pennsylvania and now headquartered in Chalfont, Pennsylvania, Datacap gives POS, kiosk, and unattended software developers a single integration that reaches a wide range of North American payment processors and dozens of payment terminals from leading . Datacap does not sell POS software and is not a merchant acquirer. It provides the layer in between: client components and APIs on the developer side, certified processor connectivity on the back end, and the device support that connects the two. Datacap holds the processor and device certifications, so its ISV partners can offer merchants processor choice without certifying to each one. :::hint{type="success"} **Get started:** Read [about Datacap](https://datacapsystems.com/about-datacap) or [request Dev Portal access](https://www.dsidevportal.com/). ::: :::: *** ::::ExpandableHeading # What is DC Direct and how does it work? DC Direct is a semi-integrated solution which embeds payments logic into (s) to facilitate a direct communication between the device and NETePay Hosted™. No Datacap hardware or software is necessary. The POS simply initiates a request through an HTTP or HTTPS POST and DC Direct captures customer cardholder data and securely sends it to Datacap's NETePay Hosted platform. DC Direct offers an optional Standalone non-integrated mode for use cases which require a Standalone payment terminal. DC Direct runs on PAX Android, Ingenico AXIUM, and PamiTV devices, and includes an optional Standalone mode for non-integrated use, toggleable on demand. :::hint{type="success"} **Get started:** Read the [DC Direct integration guide](https://archbee.dsidevportal.com/dc-direct) in the Dev Portal, or view [DC Direct compatible devices](https://datacapsystems.com/compatible-devices). ::: :::: *** ## Still have questions? - **Developers:** [Request Dev Portal credentials](https://www.dsidevportal.com/request-access) for full API documentation, transaction references, and sample code. - **Evaluating an integration:** [Contact Datacap](https://datacapsystems.com/contact-us) to talk through your platform and target markets. - **Resellers and referral partners:** [Reseller application](https://datacapsystems.com/reseller-application) - **Existing integrators:** [Support](https://datacapsystems.com/support) [title] Home [path] / [space] Suggestive Tip Prompting (/suggestive-tip) [title] Suggestive Tip Prompting [path] / ## Choose an interface: ::::LinkArray{contentSource="CUSTOM" customOrder="NmkjAuxbagp8uKS3bXbSb,e3LfN7SdRWajmWAf61qxl,YgWvc1AGvSVOwy6wO6lia"} :::LinkArrayItem DC Direct™ *Direct to PIN pad integration without local hardware or software* [DC Direct](docId\:uokv8mz14ro5OsapeOqwZ) ::: :::LinkArrayItem dsiEMVAndroid™ *Semi-integrated payments integration for Android Point of Sale applications.* [dsiEMVAndroid](docId\:QmPuPKQDiw8yuxnjFbJLA) ::: :::LinkArrayItem dsiEMVApple™ *Semi-integrated payments integration for Apple Point of Sale applications* [dsiEMVApple](docId\:Pzie4T4cvDp_pnQiMBb5w) ::: :::LinkArrayItem dsiEMVUS® *US EMV semi-integrated payments integration for PC-based Point of Sale systems* ** [dsiEMVUS](docId:82rPG2xKySD4Cp-ogaNeE) ::: :::: [title] Home [path] / [space] Surcharge (/surcharge) [title] Home [path] / [title] Go to APIs [path] / [title] Starter Projects [path] / [title] Common Use-Cases [path] / [title] Surcharging [path] / ## Choose an interface: ::::LinkArray{contentSource="CUSTOM" customOrder="NmkjAuxbagp8uKS3bXbSb,e3LfN7SdRWajmWAf61qxl,YgWvc1AGvSVOwy6wO6lia"} :::LinkArrayItem DC Direct™ *Direct to PIN pad integration without local hardware or software* [**Surcharge**](docId\:d54O23zwI5t7GoWIhcF2E) ::: :::LinkArrayItem dsiEMVAndroid™ *Semi-integrated payments integration for Android Point of Sale applications.* [**Surcharge**](docId\:C1DVsitegiCau1SVjHzQm) ::: :::LinkArrayItem dsiEMVApple™ *Semi-integrated payments integration for Apple Point of Sale applications* [**Surcharge**](docId:6U5zfYd1ELhDRYqyGxhfC) ::: :::LinkArrayItem dsiEMVUS® *US EMV semi-integrated payments integration for PC-based Point of Sale systems* ** [**Surcharge**](docId\:qSZDT-NKFDENWBo1x540S) ::: :::: ### Card-Not-Present Interfaces ::::LinkArray{contentSource="CUSTOM"} :::LinkArrayItem *Datacap's eCommerce integration to NETePay Hosted* [**What is Pay API?**](docId\:JoyfHs6137KHp_RuTVbl3) ::: ::::