In this video,
we're going to show you how to integrate Authorize.Net
to Salesforce in just a few minutes.
Let's jump in.
All right, well, first off
install both the Chargent base package
as well as the Chargent orders package.
You can put both of them into your production organization.
Next, we're going to configure Chargent.
You've got some tips in the quick start guide,
but that's really why you're on this video.
Okay, so now in Salesforce,
it's time to set up Authorize.Net.
So I'm going to start by clicking the app launcher waffle
on the upper left hand corner,
and I'm going to choose the Chargent application.
Once on Chargent, simply click the Gateways tab
then click new.
In this case, you're going to use Authorize.Net.
So we know that you do have Gateway account,
so we'll click yes on the first page.
And then we'll select Authorize.Net off the next page
and click continue.
It's time to get our keys, our login ID
and our transaction key.
If you click this link here for View Gateway Documentation,
we've got a great companion guide to this video
that will walk you through exactly what needs to happen.
It's also linked in the description below.
Okay, first we need our login ID.
So over here in Authorize.Net,
I'm just going to click account,
and then I'm going to find API Credentials & Keys.
And I'm going to click there.
In this case, I need my API Login ID,
which you'll see right here.
I'm just going to copy it and pop back over and paste it.
I need my transaction key.
So I'm just going to simply obtain a new transaction key
and click submit.
Once I've gotten the transaction key from the page,
I paste and click sign in.
Chargent's testing it.
I can see from the green tossed up here
that it's been verified successfully
and simply click continue.
Next, the Chargent setup wizard asks
if we should use Tokenization?
Chargent strongly recommends
that all of our customers use tokenization.
For more information on that,
check out our explainer video right here.
Do be sure to consult our PCI Guide for information
on complete details about configuring Chargent
to best reduce your organization's PCI scope, all right.
Next up, we've got currency.
What are you going to be using?
On the screen, you can see the most popular ones
with our Chargent customers.
Do keep in mind we support all government issued currencies
that are supported by your gateway.
Next up, are you going to use payment console?
We sure hope you will.
We think it's a very slick way to take payments.
This was letting us know
that the system is going to send an email
on your behalf requesting the key.
When you do get that, please bring that in
and put it into the system to make sure everything works.
All right, what payment methods will you be accepting?
Credit card and bank account,
sometimes known as ACH, e-check or direct debit.
And then which cards?
So sometimes folks don't want to take American Express.
So I could just toggle that off.
I want to take all of these in my org.
So I'm going to click continue.
One of the nice features of payment console
is that there's a number of different ways
that you could set up the buttons.
You may want to do your charge button.
You may want to just update the token
or possibly you need to do an authorization
or you don't need to do charge.
Simply just toggle whichever ones you need for your process.
And that's it, congratulations.
In just a quick five minutes,
you've successfully configured your new Chargent Gateway.
Let's take a look at testing next.
Okay, well, now that you've got your gateway set up
in Salesforce, it's time to do some test transactions.
And we want to do this to ensure
that Chargent was set up correctly.
And also this is a good way
to get to understand how Chargent
is going to help you take payments inside of Salesforce.
Now, this is critical to your success as a Chargent user.
You have to complete extensive testing.
Remember that this is your payment system.
No organization will survive if they cannot get paid.
And if you fail the test,
there's a good chance you won't get paid.
So please take this seriously.
At a minimum, you're going to want to create a few test charges
right now so you can see the Gateway setup guide
for some help with that.
And you can also take a look
at some of the other videos on this channel.
Okay, just a quick aside to talk about sending transactions
in the Salesforce sandbox.
So when Chargent is installed
in the Salesforce sandbox, transactions,
they're always sent to the payment gateways test account
or their developer environment.
We do this as a security precaution.
We want to prevent real transactions being accidentally sent
from your Salesforce sandbox environment.
When Chargent is installed
in a production Salesforce environment,
the test endpoint checkbox on the gateway record
will allow you to select between sending payments
to the live or the test environment.
So quick tip here, there's a few exceptions to this rule
about having different endpoints for live and then for test.
So just note that we documented them
in the companion page that goes along with this video,
which we did link below.
In those exceptions, there'll be a single endpoint
to send the transactions to.
And then there'll be different credentials
for live versus test.
It's just something we want you to be aware of.
Let's talk about transaction sync.
So Chargent has always sent charges
and authorizations to the payment gateways
and then recorded that result in real time
as a transaction in Salesforce.
Chargent can also update Salesforce records
long after the initial transaction.
So this works well for bank account transactions
that are returned non-sufficient funds or NSF
or credit card authorizations
that expire or credit card charges that are charged back.
Two fields, transaction status
and settlement date can now be updated
through a daily scheduled batch in Salesforce.
The possible values of the transaction status
are either final or non-final.
If the status is final,
then no more updates will occur for that transaction.
The settlement date field stores the date and time
when the transaction status has changed to final,
such as settled or voided.
After which it will no longer receive any updates.
So to schedule the batch,
we are just going to navigate to setup.
We're going to go to develop Apex Classes,
click the schedule Apex button
and choose the ScheduledBatchUpdateTransactionStatus.
I'm going to give it a name of transaction sync,
want it to be every day of the week.
So I've selected all of those.
It can start now
and I'm going to have it run for quite some time.
And I like to see these things updated
at three in the morning and I'll click save.
So there we go.
We have scheduled the Apex class.
Refer to your gateway setup guide
for additional information that's unique to your gateway.
Again, you'll find that in the description below.
And that's it.
We just integrated Authorize.Net
with Salesforce in record time.
Your boss is going to think you're a rock star.
Hey, if you need help with anything else, please reach out.
We're here to help.
Hey, thank you for watching our video.
And while you're here, please subscribe to our channel,
click that notification bell for immediate updates.
And if you'd like to talk payments, please get in touch.
We're always here to help.