V
V
Victor Potapov2015-02-22 19:09:39
Ruby on Rails
Victor Potapov, 2015-02-22 19:09:39

How to properly use yandex-money-sdk gem in rails?

So, the following problem arose. We tried to introduce Yandex money payment into the application. first of all, the look, of course, fell on the gem from Yandex . an application token has been received. and the api was successfully screwed. but, even when trying to make the first payment, we get
YandexMoney::ApiError
Ext action required
, the documentation says that under these circumstances, the api should return some link through which we must go, but in response we get only nil.
Does anyone have experience integrating Yandex money into a rail application? how did you connect? if there is an example, it will be just wonderful.

Answer the question

In order to leave comments, you need to log in

3 answer(s)
A
Alexander Maslov, 2015-02-26
@midikko

Hello! I advise you to use the gem from the 1.0pre branch ( link ), where errors are displayed more clearly, and how to use it is more understandable. An example of an application using the current version can be found at the link: https://github.com/yandex-money/yandex-money-sdk-r... (although there is sinatra, but it should be even clearer). Version 1.0 is separated from the release by adding documentation for a couple of classes and testing.

A
Anton Misyagin, 2015-02-27
@sunnmas

I use RoR and the gem from the link https://github.com/yandex-money/yandex-money-sdk-ruby.
I read to dock, the section: Payments from bank cards without authorization
There are three steps. After the third one, I have the status ext_auth_required , in the incoming parameter acs_uri I get a link to which I need to send a post (read here https://tech.yandex.ru/money/doc/dg/reference/proc... ). Now I need to somehow redirect to acs_uri using the POST method . How can I do this. In general, the question is what to do next after the described 3 steps ? The instruction ends, but the payment has not yet passed.

I
iBubnov, 2017-11-08
@dev-executor

case 'CHOOSE': {
      return Object.assign(state, { choosed: action.choosed }
      });
    }

This mutates the state and returns an unchanged object because Object.assign changes the state on the fly
. You need to do this
case 'CHOOSE': {
      return state =  {...state, choosed: action.choosed }
 
 }

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question