Irio / mymoip

MoIP transactions in a gem to call your own.
MIT License
31 stars 21 forks source link

Request directly for MoIP #42

Open hugomaiavieira opened 10 years ago

hugomaiavieira commented 10 years ago

@Irio when I submit my app to MoIP homologation, the told me that I have to submit the request directly to them, not from my server. So, I cant do:

request = MyMoip::PaymentRequest.new(my_id)
request.api_call(data, token: token)

They complain about that with you too?

I'm asking because it obligate us to use moip javascript (or a similar made by us) and make the PaymentRequest class useless.

Irio commented 10 years ago

@hugomaiavieira I already had approval (todays production systems) of at least 3 implementations using MyMoip following just these steps: https://github.com/Irio/mymoip/wiki/Going-alive

So, it works and shouldn't be distinguished from the js official version. Keep me informed about the next discussions. Maybe I could try to contact Moip telling them this.

hugomaiavieira commented 10 years ago

@Irio I tried one more time to submit my app following the "going alive" steps and they told me the same thing: You must send the the request directly from the navigator to MoIP. So, I'm using mymoip when possible and sending the payment request from the nagivator.

Now they homologate it.

diegoqlima commented 10 years ago

@Irio That's true that we need to use moip javascript at production server ?

Irio commented 10 years ago

@diegoqlima Unfortunately, yes. I contacted Moip to get in a better way to use it - maybe open sourcing it and accepting changes - but I didn't heard about movements in this direction in the last 6 months.

/cc @vagnerfiuza