Quickpay Integration makes it easy to setup integration with Quickpay.
It works with the latest Quickpay API v.10.

Since this is an API module, on it's own, it doesn't really do anything. But with this module, it's easy to integrate with Quickpay, and it's not dependent on any big commerce modules.
An example module is provided, which shows one way of doing just that.

Similar projects:
Quickpay (https://www.drupal.org/project/quickpay)

Project page

https://www.drupal.org/sandbox/kaa4ever/2827251

Git

git clone --branch 8.x-1.x https://git.drupal.org/sandbox/kaa4ever/2827251.git quickpay_integration

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

kaa4ever created an issue. See original summary.

PA robot’s picture

Multiple Applications
It appears that there have been multiple project applications opened under your username:

Project 1: https://www.drupal.org/node/2827253

Project 2: https://www.drupal.org/node/2813343

As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).

If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.

I'm a robot and this is an automated message from Project Applications Scraper.

PA robot’s picture

We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)

Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).

I'm a robot and this is an automated message from Project Applications Scraper.

girishpanchal07’s picture

When we installing "QuickPay Integration: Example" it's give me following error.

Also image missing on Config page.

Which Agreement id we will add on config page?
Is there payment windows agreement_id or API user agreement_id?

Where i can check payment form for QuickPay ?

It is related to webform or Ubercart or Drupal_commerce

Can you please update those issues and let us know about payment proceed URL?
Thank you.

parthpandya24’s picture

Yes i am also agreed with girishpanchal,

Can you check what is the issue? when installing module.

Thank you

kaa4ever’s picture

@girishpanchal i've fixed the configuration warning issue, and updated the descriptions for both the Agreement ID field and API Key field, so it's should be more clear.

To se a practically example of how to complete a checkout, please refer to the example module, and its readme.

The whole idea of this module is not being dependent of commerce, ubercart or any other commerce module.

kaa4ever’s picture

@girishpanchal also, I couldn't get the error you are experiencing with the images. Can you provide more information?

sandip27’s picture

Status: Needs review » Needs work

Hello @kaa4ever

I did some manual review and found :

In file: quickpay_integration.info.yml AND quickpay_integration_example.info.yml
1. Remove "version" from the info file. Later d.o adds it automatically.

In file: README.md
1. At Line # 22, no. of characters are exceeding the limit. Please re-write the sentence(s).

Thanks

kaa4ever’s picture

Status: Needs work » Needs review

@sandip27

Thank you for your comments. They have both been fixed.

parthpandya24’s picture

Hello @kaa4ever

Please update automated test error https://pareview.sh/node/126.

Thank you

parthpandya24’s picture

Status: Needs review » Needs work
PA robot’s picture

Status: Needs work » Closed (won't fix)

Closing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).

I'm a robot and this is an automated message from Project Applications Scraper.

kaa4ever’s picture

Status: Closed (won't fix) » Needs review

@krishaweb

Thanks for your comment - all the warnings have been fixed.

sleitner’s picture

Status: Needs review » Needs work

Automated Review

pareview details: https://pareview.sh/pareview/https-git.drupal.org-sandbox-kaa4ever-28272...

Git errors:

Review of the 8.x-1.x branch (commit eb7256d):

This automated report was generated with PAReview.sh, your friendly project application review script.

Manual Review

Individual user account
Yes: Follows the guidelines for individual user accounts.
No duplication
Yes: Does not cause module duplication and/or fragmentation.
Master Branch
No: Does not follow the guidelines for master branch. see pareview
Licensing
Yes: Follows the licensing requirements.
3rd party assets/code
Yes: Follows the guidelines for 3rd party assets/code.
README.txt/README.md
Yes: Follows the guidelines for in-project documentation and/or the README Template.
Code long/complex enough for review
Yes: Follows the guidelines for project length and complexity.
Secure code
Yes: Meets the security requirements
Coding style & Drupal API usage
see pareview details

The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.

If added, please don't remove the security tag, we keep that for statistics and to show examples of security problems.

This review uses the Project Application Review Template.

apaderno’s picture

Status: Needs work » Closed (won't fix)

If you are still working on this application, you should fix all known problems and set the status to Needs review. (See also the project application workflow.)
Please don't change status of this application if you aren't sure you have time to dedicate to this application, or it will be closed again as won't fix.

I am closing this application due to lack of activity.