Overview
Credit card processing in Oases is performed by using either:
- the Authorize.Net Credit card payment gateway connected to a merchant account for customers in USA and Canada.
- a Stripe Account
This article deals with The Authorize.Net payment gateway.
Article Sections
- How the money moves
- What Oases does
- Fees
- Profiles
- Signing Up
- Policy Wording
- Link to Oases
- Video - Linking Authorize.Net
- Testing
How the money moves
Accepting internet based credit card transactions requires both a payment gateway and an internet merchant account.
A payment gateway is the secure bridge over which credit card information is passed between Oases and a merchant account. The merchant account then takes the approved monies and deposits them into a bank account you have on file.
As a leader in online payments, Authorize.Net can provide you both the required payment gateway and a compatible merchant account, or just the required payment gateway that connects to your existing merchant account.
What Oases Does
Authorize.net makes it possible to take credit card payments through Oases for your services. When the payment is processed by Authorize.Net, Oases automatically allocates it to your customer's account record in the private billing module of Oases.
The transaction funds are approved in real time by Authorize.Net and then deposited by your associated merchant account provider within two to three business days depending on your terms and conditions.
Additionally, when you have an Authorize.Net payment gateway linked to Oases you can enter credit card numbers in Oases that are then stored within Authorize.Net and remain accessible via the Oases portal. This allows you to run a payment at any time from one of your customer's stored payment methods and number storage by Authorize.Net is fully PCI DSS compliant.
Fees
Credit card processing fees are charged by Authorize.Net and form part of your agreement with them for a Payment Gateway or a Payment Gateway with Merchant Account. There are no additional fees levied by Oases if you apply for your account/s via the link below.
Should you wish to link an Authorize.Net payment gateway that is not affiliated with Oases, Oases will charge an additional 0.25% transaction fee.
Profiles
You may have one or more Authorize.Net payment profile linked to your Oases database. Each account must be applied for following the instructions below to avoid any transaction fees in Oases.
Signing Up
Click Here to sign up on the Oases Authorize.net page.
1. Signing Up
To sign up for Authorize.Net for Oases it is essential to apply for an Oases Authorize payment gateway to avoid any Oases transaction fees. Do this by pressing here or copy and paste this link into your browser:
http://reseller.authorize.net/application/?resellerId=20127
Note: You must apply via the Oases link so that we may link your account with Oases, communicate with Authorize on your behalf for support issues and avoid Oases transaction fees.
Follow the instructions to apply for a payment gateway.
When successful you will receive a 'congratulations' email from Authorize.
If at anytime you need assistance from Authorize.Net for your application you may reach the onboarding team via:
- 877.320.8731 (Monday through Friday, 6 to 5 Pacific time)
- affiliatesales@authorize.net
- Quote Oases Affiliate ID - 20127
Policy Wording
2. Publish your policy wording to your website if required by your Merchant Services account.
The merchant processor provided by Authorize.Net, if taking that option, is EVO. EVO requires the following to be published to your website:
Your web site must contain all of the following information: (i) complete description of the goods or services offered, (ii) returned merchandise and refund policy, (iii) customer service contact, including electronic mail address and/or telephone number, (iv) transaction currency, (v) export or legal restrictions, if known, and (vi) your delivery policy.
This means that in your Terms & Conditions include a description of the services you provide, how you will bill for those services, when you expect payment and the currency, your cancellation and refund policy.
Link to Oases
3. Linking your Authorize.net account to your Oases database
a) When you have joined and have received your congratulations email it is necessary to log into your new Authorize account to obtain the codes that the support team will enter into your Oases database so that it may 'talk' to your Authorize payment gateway.
b) When you are in your new Authorize account go to ACCOUNTS at the top of the page.
This will open the SETTINGS page and under SECURITY SETTINGS look for API Credentials & Keys.
It may be on the left or the right depending on your account.
c) Copy the API LOG IN from the page and paste this into a new support ticket, leave the ticket unsubmitted.
d) Then copy the TRANSACTION KEY or if you are password protected request a transaction key on the page by entering your secret-question response. When the transaction key pops up copy this and paste into the same support ticket. The copy to clipboard feature does not work for everyone so copy the actual key.
e) Next press BILLING INFORMATION top left and copy your PAYMENT GATEWAY ID and paste this into the ticket.
f) Your Authorize.Net profiles may be given an account alias or nickname in Oases. This is not required if you have one profile but is essential if linking more than one Authorize.Net account.
g) Submit your support ticket containing your Gateway ID, 2 API Keys and profile Alias requesting link up with your new Authorize.Net gateway account.
Whether you have requested a new merchant account or you are linking your own merchant account to your new Authorize payment gateway you will not be able to test your account until your merchant account is fully linked.
Therefore, you may wish to wait until you have completed this step with the merchant account provider before passing us the linking API codes. This will prevent the activation of a feature that will not work in its entirety until the merchant account provider has confirmed to Authorize that all is set up.
When you pass your API codes to Oases for activation we check with Authorize that the merchant account application or linking is complete, if it is not complete there will be a short delay before activation.
Video - Linking Authorize.Net
Please press here if you don't see the video below
Testing
4. Testing your POS (point of sale) in Oases
We suggest testing your new payment gateway in Live mode with a real credit card so you can test the transaction and then void it from Oases - If voided immediately there will be no fees.
To run a test transaction in Oases:
Take your payment gateway out of test mode.
i. Log into the Merchant Interface.
ii. Click Account from the main toolbar.
iii. Click Settings in the main menu on the left.
iv. Click Test Mode under the Security Settings section.
v. Drag the toggle to Live.
a. Using test data (fake parent) open the accounts page by pressing on the total in the customer grid when accessed via Private Invoicing.
IP06. Running Payments with Authorize
b. Press on New Payment and fill out the data at the top of the payment screen selecting authorize.net as the payment method. Put the amount in pay amount.
c. Place a check mark next to the invoice you wish the test payment to be applied to and press ADD PAYMENT. If you have no invoice just press add payment.
d. From the drop down box select the card you wish to use if you have saved this data or manually enter the details of a real credit card.
e. Select process payment.
f. The payment will be entered against the customer in Oases and you will be emailed a receipt from Authorize.net. The customer will be emailed a payment receipt if you have this function turned on in Config Settings - Email.
g. Delete your payment and request a refund. This will void the transaction if not yet batched out or issue a refund if the charge has batched out. Do this immediately to avoid any fees.
h. Login to your Authorize payment gateway account and check the transaction and the void.
Link To
IP05. Entering a Payment For a Private Pay Account
IP06. Running Payments with Authorize