Payment Links allow Datacap partners to accept payments without building an additional standalone website or application. Send Payment Links via SMS, e-mail or both.

For Payment Links the authorization is the same as 

 Pay API. which consists of Basic Authorization on all endpoints as 

Authorization: Basic BASE64(eCommerceMID:ApiKey)

Payment Links API only accepts JSON. The following headers are required.

A payment link POST request consists of 6 objects:

 will contain information about the transaction like amount, tip, and line items.

 contains properties that control the look and feel of the resulting payment page.

 enumerates different types of Datacap MIDs that will be used for the payment request.

 (optional) is used for integrators to bring their own SMS provider account (Twilio supported today).

 (optional) enumerates through different ways to automatically send the payment link to the customer (email,SMS).

 (optional) will contain webhook urls and desired webhook events to be returned to the webhook page.

 sub properties here 

], 

"apiKeys": { 

//  

 sub properties here 

}, 

"communicationMethods": [ 

//  

 sub properties here 

], 

"webhookEndpoints": [ 

Pay API™

Payment Links

Payment Terminal, Pin Pad, or EMV-enabled device

payment_device

A Blind Return processes a refund for the full or partial amount. Blind returns should generally be reserved for exceptional situations, such as when the original transaction cannot be located.

Blind_Returns

Linked Returns process a refund for an amount that does not exceed the original authorization amount. Linked Returns provide several important benefits like greater security, improved approval rates, and simplified reconciliation. 

Linked_Return

ID TECH's CRC. A Cyclic Redundancy Check (CRC) is an error-detecting code widely used in digital networks and storage devices to detect accidental changes to data. 

PrePaid

A trancode is another word for the type of Datacap transaction used.

trancodes

A command that loads essential parameter and security information onto the PIN pad (payment device).


EMVParamDownload

Items

logicengine

ipport2

control

A response is the structured message returned by the NETePay Hosted payments gateway after processing a request. It includes transaction results, status codes, identifiers, and any error or validation details needed to interpret the outcome

response

A payment request is a structured API message sent to Datacap that contains transaction data, payment method details, and processing instructions required to authorize, capture, or manage a payment through Datacap’s payment services.

payment_request

PayLoader is Datacap's multi-OEM Terminal Management System (TMS) designed to streamline the configuration, deployment, and ongoing support of payment devices across merchant locations. 

PayLoader

NETePay_Hosted

Datacap's straightforward integration to ecommerce credit, ACH, gift and other card-not-present payments. Pay API uses standard HTTP methods (POST/GET/PUT), content types (JSON/XML/form encoded), and a resource-oriented architecture.

Pay_API

Payments software for Windows applications. NETePay utilizes dsiEMVUS, Datacap's Windows ActiveX control that provides applications with the ability to process electronic payments in a multi-tiered client-server architecture.

NETePay

iOS and Android libraries provide applications with the ability to process electronic payments. dsiEMVApple is an Apple framework (.xcframework). dsiEMVAndroid is an Android .aar library. 

iOSAndroid

DC Direct is a semi-integrated solution which embeds payments logic into payment devices to facilitate a direct communication between the device and NETePay Hosted. No Datacap hardware or software is necessary. 

DC_Direct

Product code of item. Use alphanumeric characters only (i.e. Latin alphabet letters and numerical digits from 0-9 ). Special characters (i.e. $, #, @, etc) are not allowed. Required to support Purchase Card Level III data. 