Sure thing... In my case. Perhaps in general.
https://github.com/AuthorizeNet/sdk-php
Installation Composer
We recommend using Composer. (Note: we never recommend you override the new secure-http default setting). Update your composer.json file as per the example below and then run composer update.
{
"require": {
"php": ">=5.6",
"authorizenet/authorizenet": "~1.9.7"
}
}
But the provided file https://github.com/AuthorizeNet/sdk-php/blob/master/composer.json is modified and not the same as the instructions and not the same as https://developer.authorize.net/hello_world/ Step 1
You will also note the Hellow World - Step 1 is out of date for the SDK...
Composer with this file content resolved for me:
{
"require": {
"php": ">=5.6",
"authorizenet/authorizenet": "~1.9.7"
}
}
There seems to be an issue as well with clear guidance for use and getting started.
For instance. After getting the SDK working, where and how to place (folder hyerarchy) for adding https://github.com/AuthorizeNet/accept-sample-app in for testing.
And one more, the https://github.com/AuthorizeNet/accept-sample-app despite havinging followed this to a T and having all requirements met... It still will not allow access with the Customer ID (and yes it is entered on my Sandbox.
How to Use the Sample App
Clone or download this repository.
Host the sample app in any web server supporting PHP, for example IIS or XAMPP (Apache). HTTPS (SSL) must be enabled for your website.
Set the authentication credentials in the application so that it uses your Authorize.Net sandbox (test) account. If you haven't yet signed up for a sandbox account, you can create a sandbox account at our [Developer Center] (https://developer.authorize.net/hello_world/sandbox/). Set environment variables for API_LOGIN_ID and TRANSACTION_KEY using the credentials for your Authorize.Net sandbox account. For example, in httpd.conf, you would add the following lines:
SetEnv API_LOGIN_ID your_id
SetEnv TRANSACTION_KEY your_key
For IIS, you could set these environment variables in FastCGI Settings -> Environment Variables.
Set the authentication credentials that Accept.js uses. Edit the acceptJSCaller() function in acceptJSCaller.js to use your API login ID and public client key for the values of authData.apiLoginID and authData.clientKey. A public client key can be created by logging into the Merchant Interface and navigating to Account --> Security Settings --> Manage Public Client Key.
Browse the application (index.php) over HTTPS connection.
To "log in", use a customer profile ID that already exists within your account or create a new one by using the Create a Customer Profile API.
In these examples, payment forms are shown in the same page and Shipping forms are handled in a separate modal popup. However, any of the types of display can be chosen to display any type of form.
While I see why all are broken up into their own repository. I think there is an oportunity to keep continuity and guidance for using / testing all. You may also note the empty README files... why include them if you have no content. The reference page https://developer.authorize.net/api/reference/features/acceptjs.html with "complete" html examples is also somwhat decieving as it does not clearly advise to what page you should post the form. Self? Also does not appear to work as when attempted no response appears to display or did I miss something in the instructions?
Perhaps I am just a bit frustrated for an out of the box experience I am use to with other platforms and examples. Finding no 3rd party reference either, and somewhat dated and lacking reference and few replies to forum posts here (excluding present thread).
Just know I'm out 2 weeks working on my project and I just need to be done and on par with learning how to use the SDK properly.
