brockf / opengateway Goto Github PK

Just to make sure we can take advantage of all it has to offer, like the autoloader, bug fixes, etc.

Support both XML and JSON as input formats. Currently supports XML for input and JSON for output.

We need to provide better, more thorough use of taxes throughout the system, including proper logging of VAT taxes. We should look at products like Magento Commerce to see how they handle it. In addition, this should be reported in the API calls.

A Notifications Center should be added to the system to allow easier viewing of multiple notifications at once, instead of notifications overwriting each other and only ever seeing one.

Email notifications on Paypal payment completion are causing the error:

Error with PHP mail(): Multiple or malformed newlines found in additional_header

This is due to message data being placed in the header area. For more info:
http://mindofdes.blogspot.co.uk/2015/07/error-with-php-mail-multiple-or.html
https://bugs.php.net/bug.php?id=68776
http://stackoverflow.com/questions/30887610/error-with-php-mail-multiple-or-malformed-newlines-found-in-additional-header

Allow for the email queue to be easily setup (how many per hour, per burst, etc.) This will need to integrate with the cronjob.

This data should be able to be sent via a ‘custom_data’ node in the API call. It is then stored in the database along with that charge information, and returned with all GET type queries through the API. It should also be made available to gateway libraries to use as needed.

By default, new clients are put into test mode which will reflect on their gateway choice, and we should dis-allow any attempts to charge a gateway that is in Live mode when the client itself is in test mode. When the client changes the mode to Live, they are asked if they want to have all of their Test data wiped out. An option should be provided to clear test data elsewhere in the system so that the different aspects of it can be cleared at any time. Live data can never be cleared or deleted unless the client itself is being deleted.

Allow for integration with PostmarkApp.com for sending of transactional emails, instead of using OG’s email system.

Payment Pages are a major new portion of the system that are designed to allow the simplest possible integration with a website to the OG system. They should function much like the external Payment pages at PayPal or Chargify.

Forms will provide basic information about the subscription being signed up for automatically and will provide options for which gateway to use, etc. based on the client’s setup.

The client can specify description text, customize logo area, font and colors.

The client can also request custom information from the users (like the Custom Fields in Hero system) that are recorded with the user.

The dataset library should be updated to allow for exporting of any dataset into either XML or CSV formats.

Provide a UI for setting the Email settings, including choosing mail(), sendmail() and SMTP settings (along with Postmark, above).

An API Test page should be provided that provides a simple way for developers (and us) to test their integration with new gateways they have developed.

The API should be reworked so that it can have different versions with different functionality. A new ‘version’ node should be included in API calls that need to use the new features. When a version is not provided, it is assumed to be a version 1.0 API call.

Coupons should record the number of times they’ve been used, which plans they were used on and by whom they were used.

A UI should be provided and it should be integrated at various points throughout the system, where appropriate.

We received a notice from Authorize.net concerning a few items that may/may not affect opengateway (or membrr). Can anyone confirm if these will require any updates or cause problems?

From Authorize.net:

RC4 Cipher Disablement

In an effort to ensure that all server-to-server communications with the Authorize.Net platform (both transactional and otherwise) maintain the highest levels of security, we will be disabling the RC4 cipher suite in the sandbox on April 29, 2016, and in the production environment on May 31, 2016.

If you have a solution that relies on RC4 to communicate with our servers, please update it to a current, high-security cipher as soon as possible. Please review our API best practices blog post for more information.

Transaction and Batch ID Reminder

In the coming weeks, due to system updates, it will be possible to receive Authorize.Net IDs (Transaction ID, Batch ID, etc.) that are not in sequential order.

For example, currently, if you receive a Transaction ID of "1000," you could expect that the next Transaction ID would not be less than 1000. However, after the updates, it will be possible to receive a Transaction ID less than the one previously received.

If your system has any functionality that expects Authorize.Net-generated IDs to be sequential, please update it immediately so that you will not see any disruptions.

Additionally, please make sure that your solution does not restrict any Authorize.Net ID field to 10 characters. If you are required to define a character limit when storing any of our IDs, the limit should be no less than 20 characters.

This way if a payment is failed, we can actually see the reason it failed, not just that it failed. This should be reported in the UI where appropriate.

md5 is extremely outdate and nearly useless with the speed of today’s computers. This needs a feature to upgrade existing accounts (like when migrating from an older system).

Allow for emails can be triggered only for a specific gateway, not for all of them. This allows users to have different wording for different gateways to match their various needs.

This logging needs to based around exceptions as well, so that when cronjobs hit an error during their execution, we can log what went wrong. This logging area should be provided in a UI that users can browse through. This should be flexible enough that it can be used by every part of the system and the UI should provide filtering by module, date, etc.

I installed it and now have errors in several places in the control panel.

in /gateway/settings/new_gateway I get this error and no way to add a gateway. Any ideas? I've tried a reinstall from scratch. Need to demo this before we buy licenses.

dataset->data)) { foreach ($this->dataset->data as $row) {; ?>

A PHP wrapper class should be provided in a single file that provides simple, robust usage for all API features in a manner that doesn't require deep knowledge of PHP to use. This makes it simpler to integrate for developers wanting to integrate into their site. This will need documentation, also.

Getting a:

00 System Error: Your OpenGateway server has not been installed. Visit yourdomain.com/install to install the server.

Looks like $server = 'https://platform.opengateway.net/api' no longer resolves.

Coupons need to have their own API integration that includes creating, deleting, updating, etc, as well as checking validity and getting usage reports.

This logging should record every transaction and some of their relevant details. Debugging logging can be provided to a ‘gateway_log.txt’ file like has been built into the last few items. This provides a simple way to see what errors went wrong when.

Alternatively, this should use the new logging class to log to the database and be browsable in the UI.

I’m not exactly sure how this works at the moment but has been requested
by a user that supports many thousands of transactions currently.

This allows a ‘client’ to operate as a single website with multiple users that are able to mange it.

Provide any additional hooks into the Hero email system as needed to meet the hooks we had in OG 1.x. I believe Hero included all of these, and possibly a couple of additional ones, but we need to verify.

Payment Pages and user area should be themeable with the Smarty-based theme system that is built into Hero (and now OG).

Not just success/failed. With a pending reason, of course.

It will be used in the call to the gateway itself.

Wanted to know of this Authorize update will effect the function of this system.

More Info : http://app.payment.authorize.net/e/es.aspx?s=986383348&e=1144558&elq=0036f88b288d491a85377fa0635a863c&elqaid=505&elqat=1&elqTrackId=b4d9a2a0f1424fe28f720ff9d8ae4d54

It might be enough to log these to files grouped by month, day, etc. or just split when reaches a certain size.

Hi
As electricfunction.com give "This Account Has Been Suspended" then i am posting a discussion and issue here
i need to integrate Secure net payment merchant with this billing engine How to going walk through...

Since we are providing a way for the user to make a payment, we should also provide the ability for them to login and update their credit card, manage their subscriptions, etc.