Chapter 1 - Introduction

Section 1.1 - Why Nuvei? link

Nuvei has partnered with Sound Payments to deliver fully-supported integrated payment solutions designed to promote and advance our partners’ success. As the first-ever community of payment experts, our goal is to create bigger and better payment opportunities for all—paving the way to great partnerships.

 

Experience our developer-friendly platform

We provide simple, developer-friendly solutions to smoothly integrate payment processing into your software or application. Our solutions will enable you to rapidly go to market and grow revenue.

  • A Single Platform to Develop, Test, and Launch

  • Developer Portal with Docs, APIs, SDKs and FAQs

  • Secure and Compliant Platform

  • Cloud-based Updates

  • Dedicated Assistance and Support

Benefit from a single, turnkey platform

We enable smart, scalable and revenue enhancing solutions that allows integrated software vendors to thrive. We support a variety of integration options, including mPOS, eCommerce, in-app or mobile.  Seize new lucrative opportunities, generate additional revenue and retain more clients by partnering with Nuvei.

 

Reduce your scope for PCI and EMV with Semi- and Cloud-Integration

Keep your transactions secure and protect your clients’ sensitive data. Our ultra-secure platform and rigorous processes reduce complexity, PCI scope and ensure bank and regulatory compliance.

Using our technology and process, ISVs are shielded from the ever-changing regulatory and compliance landscape of the card associations. Our platform manages the entire transaction via a separate, secure EMV compliant solution.

Point-to-point encryption (P2PE) ensures card data in the back office is encrypted, rendering it useless to hackers. Data is protected in use, during transfer and at rest.

 

Future-proof your payments

Our cloud-based technology automatically checks for software updates daily and pushes them to payment devices during business downtime to minimize disruption for merchants. This means fast and easy upgrades to new payment technologies when they become available, with no need to exchange or replace hardware.  

 

Enjoy dedicated assistance and integration specialists

As a network created to better serve each and every one of our partners, we deliver the best payment assistance and support in the industry. How? We focus on what matters: responsiveness, flexibility, attentiveness, and accountability. With these principles as our foundation, we are pioneering a brand-new partnership experience.

Section 1.2 - Payment Transaction Basics link

Section 1.2.1 - Credit Card Transactions link

For integrated credit card transactions, the supported business type(s) must be chosen. Most merchants will use a single business type to process transactions (i.e. a merchant operating in a brick and mortar locations will like only process retail transactions). However, other merchants may need the ability to process utilizing multiple business types (i.e. that same merchant may have mail-order and/or eCommerce website business).

 

Regardless the selected business type(s), processing credit card transaction is a two-step process. When a credit card transaction is initiated, the customer’s buying limit is reduced by the transaction amount, an authorization request is made, and that transaction is placed in a batch. A batch is a collection of approved transactions that have yet to be submitted End of Day (EOD) settlement. Funds cannot be deposited in the merchant’s bank account until a second step occurs. This second step is a retransmission of the transaction(s) for settlement. When the retransmission is processed, funding can occur.

Section 1.2.2 - Day to Day Credit Card Processing link

Each transaction can differ as well as the number of steps to complete the transaction. It can as simple as two (2) steps, i.e. get authorization, then request payment on the authorization. Other times the final amount can be different from the initial authorization, such as restaurants adjusting for the tip. Whatever the situation, we’re here to guide you through it.

 

Credit card processing usually consists of four steps,

  1. The occurrence of the day’s first credit card transaction opens the batch.

  2. Transactions are run throughout the day.

  3. At the EOD when processing is complete, it is time to prepare for settlement. This is called a Batch Close.

  4. If applicable, the merchant’s POS/ECR should initiate the settlement process. This can be handled at a preset time or manually depending on merchant environment.

Section 1.2.3 - Authorization Requests link

Authorization Requests are standard Sale or Refund transactions that occur when the credit card is swiped, inserted, or manually entered in the terminal device or POS/ECR system. The transaction data must include an amount.

Transaction amount must be sent for Sale and Refund transactions when the card data is present. This is done by setting the Amount tag. There are additional Amount tags that may need to be set whether they are a part of the original transaction or a follow-on transaction request.

 

Below are examples of tags used with follow-on transaction requests.

Tag Description
VOID Voids the original transaction and removes it from the open batch
POSTAUTH Used to complete an AUTH (PreAuth) and place it into an open batch
ADJUST Used in Restaurant settings to modify a tip
REFUND Can be used to process Refund transactions against the original transaction as a safeguard to prevent fraudulent transactions
 
Important Note
Without setting or closing the batch, the merchant will not receive any funds from credit card transactions. Check with a Nuvei integration analyst if you have any questions regarding batch settlement.

Section 1.2.4 - Duplicate Checking link

If duplicate checking is enabled by the payment processor, the processor will automatically decline duplicate transaction requests. Nuvei’s Cloud Connect Web Service has an additional feature to mitigate duplicate transactions. The override function allows the merchant to authorize multiple identical transaction, bypassing the duplicate checking feature. In this instance, a flag is checked to suspend duplicate checking.

Section 1.2.5 - Restaurant link

In traditional restaurants, a tip is added to the original authorization. Tip transactions are considered follow-on transactions and part of the original sale. A separate transaction is submitted to add gratuity to it. The TraceNum is used to accomplish adding a tip using the Adjust TransType. The TraceNum is a value assigned to easily identify the original transaction for any follow-on transaction requests. Using the TraceNum to look up the original transaction, a tip can be added using the Adjust TransType This will now authorize the processor to add the tip amount to the amount of the original transaction.

Section 1.2.6 - Gift and Loyalty Processing link

Gift and Loyalty programs are offered by Processors to Merchants in order to increase brand loyalty and boost in-store sales. Traditional store brand Gift cards are called “closed-loop” and are used in the Merchant’s location to purchase goods and services. Customers can purchase both physical cards and virtual cards, typically online, to use in-store and in a card-not-present situation. Based on the Merchant’s Gift program, cards can also be sold at other retailers in their “Gift Card Center” where these cards can be loaded to be used at the specified Merchant’s location.

Loyalty programs allow the Merchants to set up a program where their customers accrue “points” to be used for coupons or bonus items at a later time. Loyalty programs can vary based from Merchant to Merchant and the Processors offer different options for their clients. With both Gift and Loyalty programs, it is important to understand the features available for your Merchant and how their programs function.

Gift and Loyalty are Host based and do not require settlement. One thing to check is the timing of the settlement of Gift/Loyalty for your Merchants. Gift/Loyalty have a “time” cycle which is often set in minutes, usually 1,440, which is 24 hours. This is the time when the funds are released, and a new Gift/Loyalty day starts.

The basic steps of Gift and Loyalty program are this:

  1. Issuance of the card. This does not add funds.

  2. Loading of funds (RELOAD). A form of payment is needed such as a credit card or debit card.

  3. While the Issuance, Loading and Payment of the funds are technically 3 steps, you can perform the Payment, Issuance and Loading of the funds behind the scene using the API.

  4. A traditional Refund would be an UNLOAD. Choose the value to “refund” the card if necessary.

  5. Settlement occurs automatically at the Host, so there’s nothing to worry about.

Section 1.3 - Nuvei Cloud Connect Web Service Overview link

With Nuvei Cloud Connect Web Service, we provide a semi-integrated solution that gives you the ability to handle the complexities of payment device integration no longer. We have done that for you. No sensitive card data will be transmitted through your system when using our Cloud Connect Web Service API. Here’s how easy it is.

Need Help?

How can we help you today?  Our team is standing by and just a click away.