GithubHelp home page GithubHelp logo

com.ixiam.payment.redsys's Introduction

com.ixiam.payment.redsys's People

Contributors

sluc23 avatar rubofvil avatar francescbassas avatar javivf avatar

Stargazers

 avatar Javier Elices avatar Daniel Primo avatar  avatar

Watchers

James Cloos avatar  avatar Carl(it)os Capote avatar  avatar  avatar  avatar  avatar Jon Altuna avatar

com.ixiam.payment.redsys's Issues

Problems on 4.7.x versions

I'm having issues with IPN processing with the Redsys Payment Processor on a 4.7.12 installation.

After completing a contribution no mail notifications are sending to the contributor and the status of the contribution stays "Pending". If I check logs I can see errors like:

Nov 09 12:20:41  [info] Could not find payment processor for contribution record: 86

Nov 09 12:20:41  [info] Redsys Validation failed

As you can see, the problems I have are very similar with the https://issues.civicrm.org/jira/browse/CRM-17980. Alex C suggest to convert the 'payment' type extension to 'module' type (on info.xml). I'm not sure if this is possible without breaking anything or if it is necessary to rewrite the extension from 'zero' or at least doing some extension upgrade. But seems that this isn't our case because info.xml already has defined type as module.

Exception: API error: Could not delete payment processor type

I use Drupal 7.54 and Civicrm 4.5.8 and the version 1.7 module.
When I enable some module in drupal or I perform some operation in the page of extensions of CIVI I get the general error "Could not delete payment processor"
In the Drupal log I get the following 2 messages:

  1. Exception: API error: Could not delete payment processor type in CRM_Core_ManagedEntities-> onApiError () (line 396 of /home/public_html/sites/all/modules/civicrm/CRM/Core/ManagedEntities.php).
  2. $ ManagedEntities_failed = Array ([entity] => PaymentProcessorType [action] => delete [params] => Array ([version] => 3 [id] => 15) [result] => Array ([is_error] = > 1 [error_message] => Could not delete payment processor type))

The second message also appears in the CIVIcrm log in another format:

May 29 12:45:03 [info] $ ManagedEntities_failed = Array
(
    [Entity] => PaymentProcessorType
    [Action] => delete
    [Params] => Array
        (
            [Version] => 3
            [Id] => 15
        )

    [Result] => Array
        (
            [Is_error] => 1
            [Error_message] => Could not delete payment processor type
        )

)

The ID = 15 corresponds to the module I have reviewed in the database.

I have not tried to delete the module or anything, since we are using it in production. Where can I undo that command given to the API to delete that type of payment processor.

Thanks in advance and good work
Jon

Recurring Payment

My issue is not related to this project or CiviCRM. I just wanna ask you about what parameters needs to be send when doing a recurring payment (monthly subscription) with redsys? As there is very little info in the internet about this gateway

What I've currently following for recurring on initial request:

$args['Ds_Merchant_TransactionType'] = 5;
$args['DS_MERCHANT_DATEFREQUENCY'] = 30;
$args['Ds_Merchant_ChargeExpiryDate'] = '2016-12-21';

Basically my procedure currently works for basic payment but when I try with above parameters redsys outputs error saying (Offsite ofcourse)

Data error. Contact the merchant.

Any help would be really helpful. Sorry for opening an off-topic issue.

Payment.php is using short php <? tag

Payment.php file is using short php starting tag <?
In case the serve is not configured with the directive
short_open_tag=On
it won't work

Change to standard <?php tag

Bizum integration

Redsys allows Bizum payment integration. It would be nice to enable this integration within the CiviCRM Redsys Payment Processor.

Some errors in drupal log

It's a debugging warning I do not know if it will matter

Strict warning: Declaration of CRM_Core_Payment_Redsys::singleton() should be compatible with & CRM_Core_Payment::singleton($mode, &$paymentProcessor, &$paymentForm = NULL, $force = false) en CRM_Core_Payment::singleton() (línea 115 de /public_html/sites/all/modules/civicrm/CRM/Core/Payment.php).

Thanks

Payment Method not recorded

We are having problems with Redsys Payment Processor that is not recording correctly the Payment Method and makes hard to indentify payments from this payment processor.

payment-method

CiviCRM 5.10.3
Redsys Payment Processor 2.1

Add terminal code assigned to payment processor id

In case you want to have several instances of Redsys payment processor in your CiviCRM, all of these instances will be using the same terminal code defined in settings.

New feature to avoid this issue:

  • Edit Redsys settings form, where you can assign different terminal codes to each Redsys payment processor instances
  • Edit CRM_Core_Payment_Redsys, to use the terminal code assigned to the current payment processor
  • By default all new payment processor will be assigned with 001 on creation

Adapting to new 3DS2

We recently receive a notice from the bank informing about a new protocol for the payment processor authentication. They encourage us to use it to improve the payment experience for our donors.

I leave below relevant information from a technical point of view we have received:

Com adapto la meva eCommerce a 3DS2?

Posem a la teva disposició els següents manuals tècnics per facilitar l'adaptació a 3DS2 al teu eCommerce:

  • Guia actualitzada d'integració Redireccion (pots descarregar sempre l'última versió des d'aquest Link)
  • "Guia PSD2 - migració 3DS2" (pots descarregar sempre l'última versió des d'aquest Link)

DS_MERCHANT_TERMINAL non configurable

I configured recently a payment processor with "la Caixa" and they give me a DS_MERCHANT_TERMINAL = 2

This is different that the value hardcoded in the extension. It can patch as a temporary solution changing the value in CRM/Core/Payment/Redsys.php file at line 148

$miObj->setParameter("DS_MERCHANT_TERMINAL",1);

But it would be great if it could parameterize this value.

Warning: Declaration of CRM_Core_Payment_RedsysIPN::validateData($paymentProcessor ...

A warning is being recorded to the log for every Redsys transaction

Warning: Declaration of CRM_Core_Payment_RedsysIPN::validateData($paymentProcessor, &$input, &$ids, &$objects, $required = true, $paymentProcessorID = NULL) should be compatible with CRM_Core_Payment_BaseIPN::validateData(&$input, &$ids, &$objects, $required = true, $paymentProcessorID = NULL) a require_once() (línia 3 de (...)/com.ixiam.payment.redsys/CRM/Core/Payment/RedsysIPN.php).

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.