Redsys for FinDock

The Redsys for FinDock payment extension introduces support for Redsys, a Spanish Payment Service Provider operating in Europe and Latin American to FinDock. The extension adds recurring credit card payments as a payment method for Redsys.

Multi-merchantMulti-currency
nono
Payment MethodOne-timeRecurringRefunds
Credit Cardnoyesyes

Pre-requisites

  • FinDock Core (formerly PaymentHub) is installed and configured.
  • ProcessingHub is installed and configured.
  • A source connector is installed and configured.

Install and activate Redsys extension

The installation and initial setup differ from other packages. Also a specific engine account is required. Please contact support@findock.com if you plan to install Redsys. Once installed, follow the standard procedure to activate the Redsys extension.

Configure Redsys for FinDock

After activating the Redsys extension, you need to activate a payment method, deploy the configuration, and then complete the Redsys PSP settings.

To configure Redsys for FinDock:

  1. On the same tab where you activated the Redsys extension, click the Payment Methods button in the far right column and activate the payment method 'CreditCard'.
  2. Click on the Deploy-Config button. This automatically deploys the payment extension value ‘PaymentHub-Redsys’ and payment method value ‘CreditCard’ to picklists for relevant object fields.
  3. Go back to the FinDock Setup home page, scroll down to the Payment Extensions section and click on the PaymentHub-Redsys tile.
  4. Configure the Redsys settings by populating all fields with the information found in your Redsys merchant account.

Collect payments using Redsys

To collect payments using Redsys as a processor, you need to execute a bulk collection run. If you haven’t already, please take a moment to read this article about bulk collections. Although executing a Redsys bulk collection run is similar, there are some significant differences.

To run a bulk collection for Redsys:

  1. Create a payment schedule and populate at least the following fields:
    • Status = Scheduled
    • Source = For example: PaymentHub-for-NPSP
    • Payment Processor = PaymentHub-Redsys
    • Payment Method = CreditCard
    • Target = Because only one Redsys target can be configured per org, this field is inactive.
    • Collection date = A value is required. However, installments are collected immediately after executing the Payment Schedule, therefore any date can be added.
    • Run date = Today
    • Selection Date = Any date. All installments with a due date on or before the selection date are included in the run (provided they have the correct source, payment method, processor and target).
  2. Execute the payment schedule by changing the status to Generate or clicking the Start Generation button.
    • As with a regular payment schedule, in this step all eligible installments for this collection run are added to the payment schedule. This step is finished when the status of the payment schedule changes to Generated. At least the following needs to be true for installments to be added to the payment schedule:
      • The status of the installment should be New.
      • Source, payment method, payment processor values have to match the payment schedule being executed.
      • The due date has to be on or before the selection date on the payment schedule.
  3. After you’ve verified all installments eligible for this run are added to the payment schedule, click Process or change the status of the schedule to Process.
    • This step is noticeably different compared to a regular payment schedule because all installments will be sent to Redsys for processing.
      • If installments are processed successfully, they are closed as ‘collected’ and payments are created.
      • If for some reason Redsys wasn’t able to process installments, the status of these installments is set to ‘failed.’ The failure reason is recorded in the Last Status Reason field.
    • When all installments are processed, the payment schedule is set to ‘Done.’

FinDock saves the request sent to Redsys and the response received from Redsys on the individual installment records. These raw messages can be found in the fields:

  • Last Raw Request
  • Last Raw Response