Redsys

The payment extension for Redsys, a Spanish Payment Service Provider operating in Europe and Latin American, supports bulk card payment collection, as well as payments using Bizum.

Pre-requisites

• FinDock is installed and configured.
• A working connection to ProcessingHub and WebHub.
• Redsys merchant account supporting request submission forms

Install and activate Redsys extension

Follow the standard procedure for installing and activating the Redsys for FinDock payment extension.

Check and assign the required permissions. If you are using custom permission set groups, ensure the package-specific permission sets are assigned.

Configure Redsys extension

To configure Redsys for FinDock:

1. Launch the FinDock app and click Setup.
2. Click on the PaymentHub-Redsys tile under Extensions - PSP.
3. Fill in the Redsys settings as described below.
   
   • Notification URL: this value is automatically filled by the Notification Gateway.
   • Merchant Code: enter your code from the Redsys administration portal.
   • Merchant Terminal: enter your terminal ID from the Redsys administration portal.
   • Merchant Currency: enter the same currency as in your Redsys administration portal. Expected value is based on ISO 4217 number value.
   • Merchant Key: enter the same key as in your Redsys administration portal.
   • Merchant Name: enter the same name as in your Redsys administration portal.
   • Merchant Transaction Type: enter the transaction type as set in your Redsys administration portal.(See input parameters.)
   • isTest: enable if you are setting up a sandbox org. This toggle tells the FinDock which endpoint (test or production) to use at Redsys.
4. When you have entered all the details, click Save.

Bulk payment collection

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 about payment 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 = name of the source activated in your org, e.g. PaymentHub or PaymentHub-for-NPSP
   • Payment Processor = PaymentHub-Redsys
   • Payment Method = CreditCard
   • Target = this field is inactive for Redsys
   • 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 same source, processor and method) with a due date on or before the selection date are included in the run.
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.

The last step is different compared to a regular payment schedule because all installments are 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

Payment API

To test your configuration, you can use the following API messages.

Single credit card payment

{
    "SuccessURL":"http://www.success.nl",
    "FailureURL":"http://www.fail.nl",
    "Payer":{
        "Contact":{
            "SalesforceFields":{
              "FirstName":"Eric",
              "LastName":"Johnson",
              "Email":"eric@johnson.com"
            }
        },
    },
    "OneTime":{
        "Amount":15
    },
    "PaymentMethod":{
      "Name":"CreditCard",
			"Processor" :"PaymentHub-Redsys",
            "Parameters": {
            }
    },
    "Settings":{
          "ProcessingType":"Default",
          "SourceConnector":"PaymentHub"
      }
}

Recurring credit card payment

{
    "SuccessURL":"http://www.success.nl",
    "FailureURL":"http://www.fail.nl",
    "Payer":{
        "Contact":{
            "SalesforceFields":{
              "FirstName":"Eric",
              "LastName":"Johnson",
              "Email":"eric@johnson.com"
            }
        },
    },
   "Recurring": {
      "Amount": 1.23,
      "Frequency": "Monthly",
      "StartDate": "2020-06-30",
      "SalesforceFields": {
      }
   },
    "PaymentMethod":{
        "Name":"CreditCard",
			"Processor" :"PaymentHub-Redsys",
      "Parameters": {
      }
    },
    "Settings":{
          "ProcessingType":"Default",
          "SourceConnector":"PaymentHub"
    }
}