action.skip

Enabling Data Retrieval From finleap connect

JustOn integrates with finleap connect to retrieve banking transactions, which are to be stored as payment entries.

Info

The finleap connect integration is available as of JustOn 2.55 and requires at least the Salesforce Enterprise Edition.

Reference: finleap connect Data Conversion

finleap connect stores banking transactions in the figo Connect Transaction object. Upon data transfer, JustOn automatically maps the retrieved transaction JSON data to the Payment Entry object.

The following table shows which data is written to the payment entry.

Payment Entry Field Value Description
ExternalTransactionId__c FIGO + <transaction_id> External ID that is used to uniquely match a finleap connect transaction
TransactionNo__c <transaction_id> Internal finleap connect transaction ID
PaymentProvider__c figo Name of the payment provider
Status__c New Status for newly created objects
Debit__c <amount> if the value is positive The debit amount
Credit__c <amount> if the value is negative The credit amount
Reference__c <purpose> Purpose text, can be empty if the transaction has no purpose
CustomerName__c <name> Name of originator or recipient
BankAccountId__c <account_id> Internal finleap connect account ID
BookingDate__c <booking_date> Booking date
ProviderSpecificData__c complete transaction JSON data The retrieved finleap connect transaction JSON data for this object

The JSON data of the figo Connect Transaction object contains a number of additional fields. JustOn can write additional data values to custom fields of the payment entry. Each JSON value is processed in the following way:

(1) The JSON field name is converted to a Salesforce field name, where

  • underscores are removed,
  • if the JSON value belongs to a child object, the field name is prefixed with the field name of the parent object, connected by an underscore,
  • the string FIGO_ is prepended,
  • the string __c is appended.

(2) If there is a matching field on the Payment Entry object, the field value is written to this field.

(3) The type of the Payment Entry field must match the type of the JSON field value, like Text (255) for bank_name, Currency for amount or Date for value_date. JustOn automatically converts the JSON value to the type of the Payment Entry field.

Example field conversions

JSON Field Salesforce Field Name Type
account_number FIGO_AccountNumber__c Text (255)
value_date FIGO_ValueDate__c Date
end_to_end_reference FIGO_EndToEndReference__c Text (255)
additional_info.gross_amount FIGO_AdditionalInfo_GrossAmount__c Currency (13,5)

When retrieving finleap connect transactions from the banking server, the response may contain a list of deleted transactions. For these transactions, JustOn also creates payment entries with the following data:

Payment Entry Field Value Description
ExternalTransactionId__c FIGO + <transaction_id> External ID that is used to uniquely match a finleap connect transaction
TransactionNo__c <transaction_id> Internal finleap connect transaction ID
PaymentProvider__c figo Name of the Payment Provider
Status__c New Status for newly created objects
IsDeleted__c true Indicates that the corresponding transaction is deleted

Enabling the data retrieval from the finleap connect banking service involves

Adding Data Retrieval Button

To enable the option for retrieving banking transaction data from finleap connect, add the Retrieve finleap connect Transactions button to the payment entry list view. To do so:

  1. Navigate to the object management settings of the Payment Entry object.
  2. Click Search Layouts.
  3. Click Edit in the row of the List View.
  4. In the Custom Buttons section, move Retrieve finleap connect Transactions to the Selected Buttons column.
  5. Click Save to save the modified page layout.

Adding Authorization Button

To enable the option for forcing the authorization with finleap connect, add the Force finleap connect Authorization button to the payment entry list view. To do so:

  1. Navigate to the object management settings of the Payment Entry object.
  2. Click Search Layouts.
  3. Click Edit in the row of the List View.
  4. In the Custom Buttons section, move Force finleap connect Authorization to the Selected Buttons column.
  5. Click Save to save the modified page layout.

Adjusting Batch Size

The default batch size for retrieving finleap connect transactions is 100. If there are more than 100 transactions for a given time frame, JustOn retrieves the first 100 transactions directly and then starts a background process that retrieves the remaining transactions.

Info

You can monitor the background process RetrieveFigoTransactions on the APEX jobs page in Setup.

In case you encounter limit issues (CPU timeout, heap size), you may have to adjust the batch settings for the transaction retrieval accordingly. To do so:

  1. Click to enter Setup, then open Custom Settings.

    In Salesforce Lightning, navigate to Custom Code > Custom Settings.

    In Salesforce Classic, navigate to Develop > Custom Settings.

  2. Click Manage in the row of Batch Settings.

  3. Create the following new record.

    Name Scope
    RetrieveFigoTransactions 50

  4. Click Save.