Accept in-person payments on Newland terminals
Two ways in: connect the POS application you already have to a payment terminal, or build the whole payment application on the terminal yourself. Newland payment terminals are certified to PCI standards.
// Build the payment request
PaymentParam param = PaymentParam.newBuilder()
.transactionReference("500001")
.transactionType(TransactionType.CRDP)
.totalAmount("99.99")
.build();
// Run it on the terminal; the outcome arrives in the callback
RetailerManager.getInstance()
.provideFinancialService()
.newPaymentExchange(param)
.startAsyncExchange(new Exchange.RetailerSDKCallback<PaymentResult>() {
public void onResult(PaymentResult result) { /* approved */ }
public void onError(int code, String message) { /* failed */ }
});Choose your integration path
Both paths run on the same certified Newland terminals. Pick by how much of the payment flow you want to own.
Semi-integrated
You already have a POS or ECR application and just want it to trigger a payment.
PayExplorer Connect SDK sits inside your application and handles the protocol with the terminal for you. Card data goes straight from the terminal to the processor and never touches your cash register — which keeps your PCI audit scope small. Available for Android, iOS and Windows.
What you'll use
Semi-integration overviewFull integration
You're building the payment application that runs on the terminal itself.
A full stack of SDKs, from hardware and EMV L2/L3 up to a transaction workflow engine and PCI-certified P2PE. Take NSDK for a tightly coupled AAR library, or NHAL to isolate the payment application from the hardware in its own process.
What you'll use
Full integration overviewReference
Every module, one click away.