- Unzip the file to a location on your computer.
- If you installed Smart Responsive Slider from SharePoint online (Office 365) store, skip to step 2.
- If you downloaded the App file from Cotek SharePoint Marketplace for your SharePoint On-premise environment, upload the app file to your app catalog.
- Return to your site and install the add-in.
- Open the folder “SPAppLicenseCreator.exe” and click on SPAppLicenseCreator.exe file to load the app activation application.
- Fill in all the information using the activation manual as guidance (Activation manual is included in the download above).
- NOTE: The Account that you are using to activate the product should be a tenant admin account or that account should have appropriate authorization to activate apps in your tenant.
- A confirmation message should appear informing you that your site was loaded successfully and license file created successfully.
You will generally see this error message when you are trying create a new coupon code without retrieving your stripe API Key. To get a new Stripe API key, please follow the steps below:
- Visit https://dashboard.stripe.com/register
- Enter Your email address and a new password
- If you are not interested in a new stripe account, click "Skip this step"
- After creating your account, click on the dropdown beside your name, and select "account settings".
- Click "API Keys" and copy your API to OfferCommerce add-in.
- After you enter the key in the payment tab, refresh your store admin page, and finally try creating a new coupon code or making a new charge. The payment below will disappear.
NB: After you are done testing functionalities, make sure you switch your account from test to live before processing credit cards
Set up EasyPost to add automatic shipping rate calculations to your orders. If you need help after reading this, contact us today and we will help set up automated shipping calculations using EasyPost API. We have partnered with EasyPost to automatically calculate shipping costs. The Orders API allows users to represent their inventory and orders within OfferCommerce Add-in and Stripe, rather than a third-party site. If you are not yet familiar with Relay, we recommend that you first visit the Orders API Overview documentation before diving into shipping cost calculations.
To enable dynamic shipping cost calculations for your orders, simply:
- Create a new EasyPost Account
- Activate EasyPost in OfferCommerce Add-in using the administration page under "Shipping" tab.
- Or Activate easypost in stripe. See step 2 below for detailed steps.
After doing so, you can learn how to automatically generate shipping labels for your Stripe orders.
Step 1: Create your EasyPost account
If you don’t already have an EasyPost account, create one by registering at the EasyPost Sign-up Page. After creating the account and verifying your email, you can log in to your account to retrieve your API keys. From the EasyPost dashboard click the API Keys link in the left sidebar to find your keys. You will need these to activate EasyPost in Stripe.
By default, EasyPost will use USPS to calculate shipping rates. If you would like to use another carrier, you can configure additional options under Carrier Accounts in the EasyPost dashboard. Note that you will need to create an account with the carrier before you can set up the account in EasyPost. For example, you will need to set up a UPS account and store those credentials with EasyPost before you can get UPS estimates for the Orders API via EasyPost. For more information, please see the EasyPost carrier guides.
Step 2: Activate EasyPost in Stripe
To activate EasyPost in your Stripe account:
- Log into your Stripe account and navigate to the Orders Settings.
- Choose Live mode under Settings, then click Change shipping next to the Shipping setting.
- Choose Provider under Type and EasyPost under Provider.
- Enter your production API key into the fields in the form. (This is the key you found in the EasyPost dashboard.)
- Fill out the From address with the address you will be shipping orders from. EasyPost will use this address as the source address when calculating shipping costs.
- Click Update to save your credentials.
EasyPost supports both a test and a live mode for calculating shipping rates. If you want to test your integration, you can simply change your Orders test mode settings by picking Test mode in the Orders settings dropdown. You can repeat the steps above using your EasyPost Test Secret API Key to set up a test mode connection.
After completing these two steps, Stripe will automatically use your EasyPost credentials to calculate shipping costs for your Orders orders.
In addition to calculating shipping rates, EasyPost supports purchasing and printing shipping labels for your orders. You can follow EasyPost’s integration guide to learn how to automatically fulfill and purchase shipping labels for your Stripe orders.
Refunds can't be cancelled. If you'd like to charge your customer for the amount that you have refunded, you can create a new charge for your customer.
If the card that you have refunded is expired or cancelled, the customer's new card will be credited with the refund. In the rare case that the customer doesn't have a new card, the bank will usually send the refund to the customer's bank account.
In the worst case, the bank won't know what to do, and will send the refund back to us, at which point we'll contact you via email to ask how you would like to handle the refund.
We do! We provide the ability to send email receipts to your customers for any (one-time or recurring) charge, and you can see a preview of what our email receipts look like here.
Through the API
To send an email receipt for charges created through the API, you’ll want to pass in a
receipt_email with your charge creation request. We’ll then send the receipt to that email address.
We also support saving a customer’s default email address, and can automatically send receipts to that email address whenever your customer makes a payment. This is useful for recurring payments. In this case, you don’t need to pass in a
receipt_email each time you charge your customer. To enable this, you’ll want to set an
email when creating a customer, and then turn on customer receipts from your email settings by checking the box to “Email customers for successful payment.”
If you charge a customer that already has an email address attached to it, passing in a
receipt_email with a charge will override the customer’s stored email address, and we’ll send the receipt to the email address specified in your charge request’s
receipt_emailregardless of your email settings.
From your dashboard
If you (or any team member with admin or read & write privileges) are creating a one-time charge manually through the dashboard, we can automatically send an email receipt to your customer for their payment. To do this, you’ll want to provide your customer’s email address in the “Receipt Email” field when submitting your customer’s payment information through the form on your payments page.
You can also specify an email address for all charges associated with a saved customer to be sent to by specifying an email when creating a customer. To request that we send these email receipts automatically, you’ll want to turn on customer receipts from your email settings by checking the box to “Email customers for successful payment.”
For charges that are associated with existing customers, any “Receipt Email” information will override their saved email address, and the receipt will be sent there.
You (or any team member with admin or read & write privileges) can send and resend email receipts from the dashboard up to 10 times, even after the transaction occurs. You can specify different email addresses from the email address that the transaction was initially created with when sending or resending receipts from the dashboard. Your complete receipt history will be displayed on the charge’s page.
Personalizing your receipts
To customize things a bit further, you can upload a custom logo and specify some basic details about your business from the emails section of your account settings. Using your logo’s colors, we’ll automatically detect the optimal header color for your receipts, however you may override this setting by specifying a hexadecimal (hex) color referencefor the header on your receipts. The largest file size permitted for a custom logo image is 512kb. For best results, we recommend that your logo is a square image larger than 128 x 128 pixels. JPG, PNG, and GIF file types are supported.
As a note, we’ll only send email receipts for payments that are made with your live API key or through your live dashboard. If you’d like to see what a test email receipt looks like, you can click the “View Receipt” link on a live or test payment’s page. You can also send a test email from your email settings.
Receipts are automatically sent when a one-off charge that was created with a
receipt_email is refunded. When the refund belongs to a customer, however, you will need to enable the “Email customers for: Refunds” option in your email settings to automatically send these refund receipts.
Many third-party services that can be used for invoices, online storefronts for you and your customers, or to subscribe your customers to recurring payment plans also have email receipts built in, so you may want to check these out as well.
Receipts for Stripe Connect
Receipt settings from the dashboard apply to wherever the charge is made. For example, if you’ve turned on receipt notification on the platform account, then we’ll automatically send receipts for any charges made to that account. If a standalone connected account has turned on receipt notification, we’ll automatically send receipts for any charges made to that account.
You can override any of this behavior using the
receipt_email parameter; we talk more about how this works above.
Custom email receipts through the API
We’ve also given you the tools to build your own email receipts if you want to control the end-to-end experience for your customers. Building your own customized email receipts will enable you to personalize everything that your customers see, from the color of the receipt to the information that is displayed.
To implement this, you’ll want to listen for
charge.succeeded webhook events — when you receive one of these from us, you would then automatically send out your custom receipt.
If you’d like to take a peek at what this looks like in code, here is a great example.
It’s worth keeping in mind that while the
charge.succeeded event is an asynchronous way to be notified of a successful payment, our API response will always indicate success or failure, so you don’t necessarily need to wait for webhook events to determine whether a payment was successful.
To receive transfers from Stripe, you’ll need to provide us with bank account details so that we know where to send your funds. The type of information required for a successful transfer depends on where your bank is based.
Format varies by bank
Account Owner Name
|United States||Routing Number|
Format varies by bank
Countries in Beta
|Hong Kong||Clearing Code|
Countries in Private Beta
OfferCommerce is the first all-in-one eCommerce solution for swift and easy launch of a professional online store on SharePoint. You can get more information from here. Start selling online today - without breaking the bank. Features include:
Secure Payment (PCI Compliant),
Accept Cheques, Credit Cards, PO, PayPal etc
Multiple Payment Gateway
Product Variants (Color, Size, Package XYZ, etc.)
Product Search Engine
Multiple Store Views (List view, Gallery view, Grid view etc)
Highly Flexible Product Display Options
Live Shipping Calculations
And Many More Features ...
Our Live online demo illustrates our all-in-one SharePoint E-Commerce solution for swift and easy launch of a professional online store. Orders placed on this store are for test purpose since all the products listed in this store are for demonstration and testing purpose.
Your API keys are located in your account settings.
If you do not see your API keys, this means that you have either Read & Write or Read Only access, and are not an administrator for the account.
You will need to get in touch with the administrator of your account for the API keys or to request that they make you an administrator in the account's team settings.
A charge can be declined by either the customer’s issuing bank or by one your block rules, and can happen for a variety of reasons. For both of these types of declines, Stripe will show you the primary reason or risk factor for the decline to help you understand why the payment was not successful.
When we submit a charge to your customer’s bank, the issuing bank looks at various different signals including your customer’s spending habits, account balance, and card information such as expiration date and CVC to determine whether or not to accept the charge.
When a charge is declined by your customer’s bank, we show as much information as we receive about the decline in your dashboard. Unfortunately, most decline reasons are generic, so we don’t have much specific information as to why a charge was declined. If all of the card information seems correct, it is best to have your customer contact his or her bank, inquire for more information, and ask that future charges be accepted.
At the core of Radar, Stripe’s modern suite of fraud protection tools, is our machine learning system that evaluates all your credit-card based on transactions for fraud. Those transactions we believe are highly likely to be fraudulent are labeled as high risk (highest in our API) and are automatically blocked. These charges are noted as “Payment blocked due to high risk” in the payment detail view and we will also include the primary risk explanation for why the charge was evaluated as high risk.
A charge could also be blocked by one of your custom rules you’ve setup through your rules dashboard. For any of these payments we will note that the payment was blocked by one of your custom rules, and which rule blocked the payment.
Decreasing the likelihood of declines
If you are confident that a high risk payment that was blocked by Stripe is actually legitimate, you can report the charge as safe in the Dashboard. After marking a payment as safe, you (or your customer) can retry the payment–Stripe will react to your feedback accordingly.
Other actions you can take to decrease the likelihood of declines are helping the customer pass through correct credit card number, expiration date and CVC code by adding in validation checks before the customer submits his or her payment. (eg: Did the customer enter in a valid future date when entering an expiration date?). Collecting the CVC can also significantly decrease your decline rates. If you’re not collecting CVC’s and having issues with declines, requiring the value can be a quick & easy fix.
Other additional data you can collect from the customer, such as name, address or billing zip code, can help with decline rates - but impact can vary by credit card brand. If you continue to experience issues with declines, it might be worthwhile to try to collect some of this additional data.
Immediately after installing OfferCommerce Add-in, you might see the following message.
"Error occured while loading your store administration page. Please contact Site Administrator. If problem persist, please visit www.OfferCommerce.com for support.
Access denied. You do not have permission to perform this action or access this resource."
The message indicates the app was not given the proper permissions. So you will have to follow the instructions below to resolve the issue;
- Go to Site Content and hover over OfferCommerce Add-in image.
- An ellipsis will appear as shown on the screen shot below;
- Click on the three dots and click PERMISSIONS.
- When the window opens, click on the little hyperlink at the bottom of the add-in icon to trust the app. See screen shot below. If the problem persist, please send us an email at firstname.lastname@example.org
Radar is a proprietary suite of tools, based on our machine learning algorithms, to help you maximize revenue by catching fraudulent charges and minimizing declined payments. Radar is available to all users who have implemented client-side tokenization via Stripe.js, Checkout or our supported mobile SDK integrations (iOS and Android).
- Machine learning: Radar employs advanced, adaptive algorithms that learn from a large global network of businesses. Radar scans every payment against the most relevant signals and automatically blocks or flags fraudulent transactions.
- Risk Evaluation: Radar provides real-time insights about fraud for your business and provides granular info about why payments were blocked or flagged.
- Rules: Reflect your unique business logic by using custom rules to block or flag payments for review by your teams.
- Review: Simple workflows in the Dashboard to give unusual payments a second look.
For businesses looking to enact highly specific fraud controls, you can create rules to manage how your business handles incoming payments. For example, you may want to allow all charges under $5, or flag charges with certain characteristics for review. You can see our documentation for more on setting rules.
That said, even with all these checks, fraud can still slip through the cracks. We very much want our users to be as informed as possible, both so that they can accept or refund any charges they believe are fraudulent and so they are equipped to accept the financial responsibility of any suspect charges that enter their Stripe account. Working together, Stripe’s tools and your vigilance make a strong team to combat fraud.
Add B2B and B2C sales order and management processes and shopping cart capabilities to your SharePoint site (internal sites only on Office 365 sites and both internal and external sites on premise SharePoint). Process credit card transactions on your site. Your customers will never leave your site. Calculate real-time domestic and international shipping from your site.
Organizations also use OfferCommerce to create company classified ads for employees. Employees can buy and sell personal belongings from their intranet portal.
Give your online shoppers and employees a smooth ride all the way from the shopping cart to the secure checkout process.
1) The license costs nothing.
2) You need a decent technical expertise or a hired specialist to install all the add-ons/skins you need and make them work together on your server.
3) When a security patch is out you need to either pay a good deal for the update and making your store work after that, spend days/weeks on it yourself or risk the store being hacked.
4) The hired developers often tend to tie you up the way that you either pay monthly or your store breaks.
5) If you need support, there’s only community which has no particular reason to answer you at all and carry no responsibility when they do.
7) When you’d want to accept credit cards right on your website to improve conversion you’ll need to either migrate to $3500+ a year plan, losing number of your features, or just forget about it.
1) To start you just need to install the app by one click of a button.
2) When you need to upgrade/update the store, click just one button and the software handles this automatically.
3) When you need an extra feature you can have us build it for you.
4) When you need assistance can call us 24/7 and they will be someone on the phone to help. You can also choose between community, which is very active by the way, and offer technical support.
5) When you need to accept credit cards right on your website, you simply sign up for Stripe Payments, by entering your email and password. It's that simple.
This is where we'll be sharing our thoughts on topics that matter to us. Who knows... we will even post screenshots, videos and links to other interesting stuff.
If we catch your interest, please let us hear from you.