Within the Settings section of Ordergroove, you can configure your shipping, credit card, and subscription creation validation settings.
Note: Please review these changes carefully before saving them as they control your program's critical functions.
Shipping
- Countries
The country options that you want to make available for shipping. Please note that Ordergroove currently only supports a small handful of countries. - Shipping Rate
- Flat Rate
Clients can use this option to set a universal shipping rate for all orders.
- Flat Rate
-
- Country-Specific Rates
Clients can use this option to configure different shipping rates based on location so they incur the lowest possible cost when shipping. To use this a Client needs to first enable the available countries in the Shipping section at the top of the page.
This solution requires Clients to have flat shipping rates. Clients will not be able to set variable shipping rates (e.g. weight-based, dynamic.) for subscriptions. This solution also does not enable Clients to offer different shipping method options (e.g. ground, express) for subscriptions.
- Country-Specific Rates
- Combination Savings
Defining a sensitivity (e.g., five days) within which the next order closest in date will be combined with the current order before placement on the eCommerce platform. This feature helps reduce shipping costs and will merge orders at the time of the Order Reminder email.
A maximum of two orders will be combined, and only if using the same shipping address and payment record. The order with the later ship date will be merged with the order with the nearer ship date.
Credit Card Validation
- Retry orders which failed due to bad information
You can help minimize churn by turning on a feature that will retry orders which have failed due to invalid payment data. When an order is rejected, for this reason, Ordergroove should receive a response from your endpoint regarding the rejection and will trigger an email to the customer notifying them about their failed order, instructing them to log in to their account to update their payment information.
Ordergroove will attempt to replace the failed order 2 additional times on the 3rd and 6th day after the original order date, in an attempt to allow the customer time to update their payment method. If the payment method is still invalid during the final attempt to place, it will be marked as rejected in our database. - Refresh credit card expiry to ensure subscription continuity
If Ordergroove is hosting customer payment data, you will see the option to Refresh credit card expiry to ensure subscription continuity. If turned on, Ordergroove will extend the customer’s default-but-expired credit card date three years into the future in an attempt to process the order successfully.
However, the feature cannot be utilized if your payment processor is storing customer payment data, as the payment information passed back in the Order XML will not impact the credit card expiration that your payment processor stores.
The new expiration date will only be extended in Ordergroove’s database. The customer will not see the updated expiration date in any UI unless they manually update their default payment method within the billing section of the Subscriber Dashboard. If this feature is being used, Credit Card expiry emails won’t be triggered because card details will have been refreshed within the system.
Subscription Creation Validation
You can configure the fields sent to Ordergroove by your integrated eCommerce platform upon subscription creation. If unsure of what to select here, please review your platform-specific integration guide or submit a support request through our portal.
Each field is critical: New subscriptions received without the data configured as required will fail due to missing information.
- Payment
While a payment method is required for all checkouts, Ordergroove does not require payment data to be sent during subscription creation. However, if you want to use the Refresh credit card expiry to ensure the subscription continuity feature, Ordergroove will require the customer’s credit card expiration date.
Note: The Update Default Payment API must be configured and working within the customers' payment wallet for Ordergroove to sync with the customer's selected default payment method.
- Payment Method Required: Requires purchasePOST to include payment information for each transaction sent to Ordergroove. Each selected field must be provided at checkout, or the purchasePOST will fail.
- Pending the information you will need to receive back within the Order XML, you can require all payment fields to be sent within the purchasePOST. If Ordergroove is hosting payment, please contact the support portal to discuss the fields required.
- Token ID: Customer payment token. On many platforms, the token ID will be the same as the customer ID in your database. During order placement, the token ID is sent back to your endpoint to tap into the customers' payment wallet and charge their default payment method.
- Card Holder: Name on the credit card.
- Card Number: The last 4 digits of the credit card. Data will be AES encrypted within the purchasePOST.
- Card Type: Credit card type. The card type will be sent in numeric form and map to the below card type in Ordergroove’s database.
- 1: Visa
- 2: MasterCard
- 3: American Express
- 4: Discover
- Card Expiry: Credit card expiration date. Data will be AES encrypted within the purchasePOST. The format must match mm/yyyy.
- Card Label: Should be left off unless otherwise instructed by your Ordergroove Support Team.
- Card Type and Card Holder must be optional if turned on.
- You will need to check with your eCommerce provider regarding the storage of user billing agreements to charge recurring orders.
Note: You will have the option to display the last four digits, expiration date, card type, and name on the customer’s default credit card within transactional emails and the Customer Self-Management Interface. Displaying the customer's chosen default payment method helps eliminate customer confusion about which payment method is being charged.
Ordergroove does not support alternative payment methods (PayPal, Apple Pay, Google Pay, After Pay, etc.).
If your payment processor needs specific payment data to charge customer orders at the time of order placement, the required settings will need to be turned on to ensure the data is sent within the order XML.
- You will need to check with your eCommerce provider regarding the storage of user billing agreements to charge recurring orders.
- Payment Method Required: Requires purchasePOST to include payment information for each transaction sent to Ordergroove. Each selected field must be provided at checkout, or the purchasePOST will fail.
- Customer
This section governs the customer data sent to Ordergroove, which will become mandatory going forward for each transaction. Customer data should be required for account and display purposes.
- Customer Required: Requires purchasePOST to include customer information for each transaction sent to Ordergroove. Each selected field must be provided at checkout, or the purchasePOST will fail.
- First Name: Customer’s first name.
- Last Name: Customer’s last name.
- User ID: Customer’s ID on your database. It can be the same as the Token ID from the Payment section.
- Email: Customer’s email address.
- Billing Address
The Billing Address section allows you to select the billing data to be sent to Ordergroove at checkout. If any of the fields will be required during recurring order placement, ensure they are turned on for purchasePOST.
- Billing Address Required: Requires purchasePOST to include billing address information for each transaction sent to Ordergroove. Each selected field must be provided at checkout, or the purchasePOST will fail.
- Note: if all customer's billing information is needed to process and order, or if Ordergroove is hosting payment, all billing information should be sent within the purchasePOST.
- First Name: Customer’s first name on CC.
- Last Name: Customer’s last name on CC.
- Address: Customer’s CC billing address.
- City: Customer’s CC billing city.
- State: Customer’s CC billing state.
- Zip Code: Customer’s CC billing zip code.
- Country: Customer’s country code. Ordergroove only supports domestic (United States) addresses. Other countries should be restricted at checkout.
- Billing Address Required: Requires purchasePOST to include billing address information for each transaction sent to Ordergroove. Each selected field must be provided at checkout, or the purchasePOST will fail.
- Shipping Address
- The Shipping Address section allows you to select the shipping data to be sent to Ordergroove at checkout. If any of the fields will be required during recurring order placement, ensure they are turned on for purchasePOST.
-
- Shipping Address Required: Requires purchasePOST to include shipping address information for each transaction sent to Ordergroove. Each selected field must be provided at checkout, or the purchasePOST will fail.
- First Name: Customer’s first name.
- Last Name: Customer’s last name.
- Address: Customer’s default shipping address.
- City: Customer’s default shipping city.
- State: Customer’s default shipping state.
- Zip Code: Customer’s default shipping zip.
- Country: Customer’s country code. Ordergroove only supports domestic (United States) addresses. Other countries should be restricted at checkout.
Comments
Please sign in to leave a comment.