At Acespritech, we have developed many payment gateway integration with Odoo. Here we have one more integration with Odoo i.e Stripe payment integration.
We have added new “Stripe” TAB into customer form where we can register on stripe and generate tokens by registering credit card information. By default when new customer will register into Odoo, it will register on Stripe server also.
We can register more than one customer easily.
After registering customer successfully on stripe, user can register credit card information and generate tokens. For security reason, we are not storing credit card details into database.
We can check same card information on stripe server.
It is very easy to delete registered token from Stripe server and Odoo.
We can easily find registered customer also by applying filter.
Added new field for processing on stripe server with accounting journals and differentiate with normal transactions.
After invoice validation, during payment process in customer invoice, there will be Card selection field available.
After successful transaction, it will appear on Stripe server as well as complete payment process in odoo.
We have implemented Stripe functionality with Portal. Once we sign up by Odoo, it will create
customer and also register it on Stripe server automatically.
For security purpose, Customer will easily registered their card on Stripe server and generate tokens.
For example, you made a sale on credit to a customer, but one week later the client’s business declared bankruptcy and became completely unable to pay off the credit account with you. This uncollectible debt would then be written-off by your company and recorded as an expense by accountants.
Here we are going to take an example of “write off” for sale in OpenERP. Create customer invoice and validate it.
It will create sales accounting entries like below.
Now we are getting some amount from customer as a part of his invoice.
Still there are some balance customer has to pay.
This is customer’s partial payment entry.
Now, customer is telling that he will not pay remaining amount for any reason. So it require to make settlement for our accounting means make write-off on customer invoice.
From journal item, we are selecting original sales and payment entries and using “Reconcile Entries” option.
Here we can check remaining balance that we are going to write-off.
Here we have very important option available. We have to select proper journal and account where entries will occur.
After reconcilation, there is no due amount to take from customer and invoice become PAID.
After this development we have implemented eCheck feature for authorize.net integration with many other imporvemets. In newer version, it will be possible to add more than one credit card numbers for customer. And it is also possible to insert new credit card information during payment process.
Same as credit card, user allows to enter more than one bank information of their customers and can create during payment process.
Here we have made major improvements compare to older version. User can select better option for payment request from popup window like ‘Credit Card’ or ‘Bank’ and related options will also be appear.
There are other methods also available with eCheck but Authorize.net Test account allow to make testing with below two methods only.
After make payment request with eCheck, authorize.net server gives some response.
We are keeping histrory of each and every transaction with response that generates with Authorize.net.
It is very easy to STOP payment which is already sent to authorize.net for further processing.
And once transaction will settle with authorize.net, you can refund it with any amount.(less than Invoice amount).
We have implemented solution for allowing payment process via SagePay from OpenERP. We will see how this module is developed.
We will start from configuration of SagePay account information. It is very important to select appropriate “MODE” of SagePay account.
It is possible that customer may have more than one credit cards. We can configure credit card related information into Customer form itself. We are storing credit card number into database with encrypted format.
To process with sagepay, we have added option into OpenERP voucher form. We can easily make payment or stop it from here.
We are allowing to make three types of transactions with SagePay from OpenERP.
Further process will work according to selected transaction.
After making process, SagePay server will give response about transaction and we are storing that into database for future actions.
We are storing mainly following data:
– Transaction ID
– Transaction Status
– Transaction Message
Now It is very easy to stop your transaction for any reason.
We are restricting user to make any invalid actions on transactions.
It is displaying VOID response from SagePay server. It is possible to perform on transactions which are registered with SagePay.
As mentioned above, it is possible to ABORT only DEFERRED transactions.
We are getting status “REGISTERED” for AUTHENTICATE type of transaction. And that transaction has to AUTHORIZE with SagePay.
We are keeping record of each and every transaction with detail information in OpenERP.
This is how SagePay Simulator page looking.
Here we have to Add IP address of our server or machine from where we are accessing our SagePay account through API. And also add appropriate Currency code for allowing transactions.
It is displaying list of transactions that is related with our account.
Recently we have made integration with OpenERP with Authorize.net for payment services. Now we have integrated OpenERP with another Payment services, BluePay. We can have more information from http://www.bluepay.com. With help of this module, it is very easy to process with credit card from OpenERP interface.
First of all we have to create account on BluePay and get required information and use those information to connect with BluePay from OpenERP. We have tested each transaction in TEST mode.
It requires credit card information to make transactions. We are storing required details into Customer form. We are using AES algorithm for securing credit card number into database.
Sometimes it is require to know that customer has enough balance in his credit card or not. We are giving facility that user will enter amount that he has to check for particular customer and get relevant message.
As we are storing credit card number in a secure way in database so it is not allow to change credit card number directly.
We have improved GUI of voucher for sending payment request to BluePay. It allows to send request only one time if it will succeed. And also stroing transaction related information into voucher for future purpose. It will cancel payment request with BluePay if we are going to cancel voucher.
Sometimes it is require that customer wants to pay amount in installment. We are allowing to create recurring payment request with BluePay.
We are keeping track of messages for each and every transactions occur during recurring payment.
User can change any parameter during recurring payment process execution. And can cancel it also.
We are tracking details of each and every transactions with BluePay.
User can print transaction details on PDF report by entering date range and proper parameter selection.