Would you like to work together?

[makasim]

I am working on a payment library: https://github.com/Payum.

There is a bundle for it: https://github.com/Payum/PayumBundle, sandbox https://github.com/Payum/PayumBundleSandbox

I am looking forward to hear your answer?

[dominikzogg]

Hello @makasim

Do you mean a saferpay implementation for payum?

Regards @dominikzogg

[makasim]

Do you mean a saferpay implementation for payum?

Yes, in general. I think payum provide solid background for different payments so maybe you may be interesting to migrate to payum?

[dominikzogg]

I have not the time at the moment to write it, maybe you could prepare
something?

Am 14.03.13 11:57, schrieb Maksim Kotlyar:

Do you mean a saferpay implementation for payum?

Yes, in general. I think payum provide solid background for different
payments so maybe you may be interesting to migrate to payum?

—
Reply to this email directly or view it on GitHub
#2 (comment).

[makasim]

what kind of preparation do you mean? Create a skeleton or?

[dominikzogg]

We worked also with the
https://github.com/schmittjoh/JMSPaymentCoreBundle and it was not easy
to write a "payment provider bridge".
If you have a skeleton this would me to see, how good an implementation
can be and how much it takes.

Am 14.03.13 13:28, schrieb Maksim Kotlyar:

what kind of preparation do you mean? Create a skeleton or?

—
Reply to this email directly or view it on GitHub
#2 (comment).

[makasim]

ok, I see.

how good an implementation

I had started to work on Payum after I worked a lot with jms payment. I know internals of jms payment very well. I did also some pull request to it (with refactoring). Then I realized that jms payment is far from what I had in mind. When I worked on Payum I kept in mind all of what I learned from jms payment.

The implementation could be really good, and this is why:

• It is easy to use (you can look at sandbox).
• Everything decoupled. (Example: https://github.com/Payum/PaypalExpressCheckoutNvp/blob/master/src/Payum/Paypal/ExpressCheckout/Nvp/PaymentFactory.php).
• Storage support out of the box (https://github.com/Payum/Payum#how-to-persist-payment-details)
• there is working bundle.

About implementation and time it may take:

• Create saferpay repo with skeleton about 2-3 hoours
• Create CaptureAction - 4 hours
• Create StatusAction - 4 hours
• Create PaymentInstruction - 1 hours
• Create PaymentInstruction entity for Doctrine - 0,5 hours
• Create PaymentFactory to integrate to bundle.

In general this it.

I am going create a skeleton repo in payum If you think we can move this direction.

[dominikzogg]

Let me take a look this weekend, sounds good

[dominikzogg]

@makasim I didn't found the time, to watch at payum, so i have to take a look next weekend (this project is not payed by a company)

One question: Do i have the possibility to get the data of every step at every time, cause my payment lib reads data from step 1 in step3?

[makasim]

I didn't found the time, to watch at payum, so i have to take a look next weekend (this project is not payed by a company)

It is ok, this is also a hobby for me.

One question: Do i have the possibility to get the data of every step at every time, cause my payment lib reads data from step 1 in step3?

Everything stored in a model (currently supported doctrine orm and filesystem storagies). So you could access that data all the way.

[makasim]

I've created a saferpay repo with classes to be implemented. There is also a PR to payum bundle. As you see it is not much to do to integrate the lib to bundle.

Do you want me to grant you access to the repo?