Set up and manage Gateways, Payment Apps, and more
29 Next supports 120+ global gateways for payment card transactions. If you don’t see your payment gateway listed as supported, just ask us.
29 Next Payments
Stripe Payment Intents
To add 29 Next Payments to your store, navigate to Settings > Payments. Under Payment Accounts, choose Create New Account.
You will be redirected to the onboarding flow to provide account setup details. Once an account is approved it will automatically be loaded under Payment Accounts, and available for live transactions, including use with Gateway Groups.
To add a Gateway, navigate to Settings > Payments to see a list of all gateways. Under External Gateways choose Create Gateway to add a new gateway.
On the following page, select the desired gateway integration and add your gateway specific access credentials to integrate the Gateway to the store. Note that these required fields for specific gateway integrations may vary.
Once a Gateway has been added to your store, you can specify
- Currencies Supported
- Accepted Card Types
- Payment Flow (Charge, or Authorize & Capture)
- Enable 3DS support, and assign a 3DS Merchant Profile to the gateway
The Default Gateway for a given currency will automatically be selected on the storefront checkout or for API-created orders, for transactions in that respective currency.
To use multiple gateways on the storefront checkout, create a Gateway Group, and assign it to your storefront checkout via Settings > Payments > Settings > Default Gateway Group.
For orders created via the Admin API, you may optionally define a
payment_gatewayID to route the transaction to a specific gateway ID via the
payment_details > payment_gatewayparameter.
Stores with multiple bankcard gateways may wish to distribute transactions across them on a proportional basis. With Gateway Groups, you can assign multiple gateways to a single group, and define a weighting to each gateway to prioritize the distribution of transactions.
To create or edit a Gateway Group, navigate to Settings > Payments and choose the “Gateway Groups” tab, then Create Gateway Group to create a new gateway group. Alternatively, from this view you can choose to Update or Delete existing groups.
On the create new gateway group page, assign one or more existing gateways to the group, and choose a weight for the proportion of transactions that should be directed to each of them, with the higher weights receiving the higher proportion of volume.
Transactions pointed at a gateway group will select from the gateways, based first on the availability for the given card type and currency, then on the weighting assigned to the eligible gateways. This rule prevents a gateway that does not support a given card type or currency from being selected to process a transaction.
For orders created via the Admin API, you may pass a
payment_gateway_groupID in the
payment_details > payment_gateway_groupparameter. If a payment gateway group ID is specified, it will override the default gateway, or any value input into the
To use a Gateway Group for your storefront checkout, assign it at Settings > Payments > Settings > Default Gateway Group. If you assign a Gateway Group it will override any previously configured "Default" gateway for each currency.
If your payment flow includes gateways supporting 3DS2, you should always specify a
payment_complete_urlin your API request. Read more about supporting 3DS2 transactions over the Admin API here.
29 Next supports a variety of Payment Apps, including Bankcard (all debit and credit card processing gateways), Paypal, and Klarna.
29 Next supports over 120 global payment gateways for Bankcard processing, which encompasses transactions via credit and debit cards such as Visa, Mastercard, AMEX, Discover, Maestro, JCB and more. Bankcard Transactions are available for review in the Dashboard by navigating to Payments > Transactions, with the full details of each transaction passed to an underlying payment gateway and processor, along with the full response returned by the gateway.
View the list of all payment transactions by navigating to Payments > Transactions. From this view you can filter and export lists of transactions to CSV by selecting Actions > Export to CSV.
Transactions can be searched by using the Advanced Search feature. Choose Filter and select to filter the transactions list by one or more of the following parameters:
- Transaction ID
- Date Range (From / To)
- Type (Authorize/Debit/Refund/Void)
- Subscription Lifecycle
- Card BIN (card first 6 digits)
- Card Last 4
- Gateway Group
- Amount of Transaction (From / To)
- Response Code
- Status (Success / Fail)
- Is Disputed (Yes / No)
- Is 3DS (yes/no)
- SCA Flow
Additionally, filter transactions by any Marketing Source Attribution values that are connected to the Order for which a transaction was made.
Clicking on any Transaction ID, or the View button from the Transactions List View will show the Transaction Detail. Transaction details provide all information available for the transaction, including the raw transaction data sent to the payment provider or gateway, and the data returned in response.
Choose Actions from this view to apply a Refund (or Void) to a transaction, or mark a transaction as Disputed.
To manually Capture an Authorized transaction within the authorization period, choose Actions > Capture Payment.
Paypal is a Payment App that offers a variety of Paypal features both in the store checkout and for orders created over the Admin API.
Both the legacy Paypal Express (SOAP/NVP) integration and the Paypal REST integration are supported. Paypal REST API is the default integration method and the method most commonly used by sellers.
Under Apps > Paypal, configure Paypal features and input your Paypal API account credentials. For testing purposes, set the “Environment” to Sandbox. When you’re ready to accept live transactions, be sure to switch the Environment to “Live”.
29 Next supports automated uploading of shipment carrier and tracking number information to Paypal for Paypal sales. Uploading tracking data to Paypal is recommended to minimize the risk of disputes and provide the best customer service to Paypal buyers.
To allow for post-checkout one-click upsells for Paypal buyers, without requiring a second redirect or Paypal confirmation pop-up, your account must be enabled for Reference Transactions.
- Reference transactions are only supported via the legacy NVP/SOAP Paypal Express integration.
- Reference transaction support is not enabled by default for Paypal accounts. You must request this to be enabled via Paypal support for your account.
- This process may take several days, and Paypal may request additional information from the merchant to approve this request.
Paypal Admin API Guide
Klarna Checkout is a Payment App that allows you to offer multiple payment options for customers to choose from, both in the store checkout and for orders created over the Admin API. Klarna is a popular payment platform in Germany, and increasingly in the UK and across Europe and the United States.
Under Apps > Klarna, input your Klarna Checkout account credentials to enable Klarna. Note that Klarna requires your store to have a Terms & Conditions URL and a Cancellation Policy URL available at all times, reflecting the store’s sales policies.
Via Klarna Checkout, various checkout options are available for the end customer, depending on the customer’s location.
- Pay by Invoice
- Pay Later
- Pay in Installments
- Sofort Banking
- SEPA Direct Transfer
- Credit and Debit Card
Klarna Admin API Guide