Could you please improve developer documentation?
- The hook docblocks do not document the properties that need to be returned.
- hook_pay_method_handler_info()'s name says the hook is about handler information, but what handlers and where are they defined?
- Can you write a short list of steps to write a payment method for Pay?
- What exactly are modules expected to add to user's settings form?

Comments

daglees’s picture

Any updated on this?

stenjo’s picture

Assigned: Unassigned » stenjo

I have started a documentation page How to write a payment module to Pay payment API
Would be good if more people could chip in with corrections and suggestions on improvement.

daglees’s picture

Great job sten, I'll help out.

stenjo’s picture

Having read the module description - particularly the part about:

Please contact the maintainer if you think this module will work for you, but you need additional help, advice and functionality not already included here.

I have now contacted the module maintainer twice via the Drupal.org user contact page without any response whatsoever.
Either that feature is switched off for that user or she is too busy to answer.
To be able to continue building the documentation page referred in #2 I need a few lines from someone knowing the module architecture inside out that indicates how a new payment method should be implemented. I do not need much, but as a minimum:

  • What methods should be implemented/overridden/added
  • What is the flow of control
  • What is the ideal way of implementing the payment method (inheritance/interface implementation)

Any clues anyone?
I am not a pro PHP developer but I know the basics of object orientation and PHP. I have spent hours trying to get my head around how the payment methods are plugged into the Pay module with limited success.
I need a push in the right direction here.
/Sten

gdoteof’s picture

I have also spent a fair amount of time tyring to understand this. Did you get anywhere stenjo?

stenjo’s picture

I'm sorry no. I had to abandon the development of my interface to this module as it would be too much work trying to get my head around this without some documentation.
If you do find the time to spend, please write a few lines about what you have discovered in the documentation pages.

stenjo’s picture

- double post

xano’s picture

The lack of documentation was one of the reasons why I developed Payment as an alternative to Pay. You may want to look at its handbook page or the API documentation to see if it fits your needs.

stenjo’s picture

Thank you Xano, I think this may fit perfectly :-)
I was not aware of your module, but sure seems to be something our Tripletex module should be talking to.
I'll get back to you (n your issue queue) when we have something ready.