Skip to content

Payments/Payouts Concepts

payment_app_intro JustOn Cash Management is a Salesforce app that integrates Salesforce CRM with European banks and payment service providers. The app allows you to trigger payments and track payment information related to your business with customers.

You will be able to prepare and execute payment operations based on your orders, invoices or other statements that involve payments or payouts, as well as to retrieve information on processed payments and to associate it with the corresponding accounts receivable or accounts payable. Broadly speaking, JustOn Cash Management helps reconcile accounts.

Understanding Payments

Businesses sell and purchase products and services. These operations involve payments or payouts – generally, money due to receive from buyers for a sale, or due to pay to suppliers for a purchase. Specific use cases may also involve credits or refunds.

pay_app_payment

Payments/Payouts in JustOn Cash Management

JustOn Cash Management summarizes receivables and payables as entries, based on which you trigger the relevant payment operations. Technically, you process the payments or payouts via a payment provider integration or a connected bank account.

In this context, the following objects are important:

Payment
JustOn Cash Management uses payment records to track a money transfer and its status.
Payment item
A payment item represents the recorded money transfer operation for a payment processed via a payment provider.
Bank statement item
A bank statement item represents the recorded money transfer operation for a payment processed via a bank using EBICS.
Bank statement
A bank statement represents the daily collection of bank statement items for one bank account.

To hold the data that is required for processing collections, the following objects are relevant:

Business entity
The business entity represents the legal entity or organization "doing business".
Payment instrument
A payment instrument is a SEPA mandate or a credit card handle that allows the business entity to collect money from a customer.
Payment provider
The payment provider represents a service provider that executes collections (accepts and processes payment operations) on behalf of the business entity.
Bank account
Bank account records hold all relevant information on actual bank accounts, through which business entities can execute EBICS-based transactions.

For an overview of all objects that are relevant for JustOn Cash Management, see Object Model.

Payment Provider Integration

JustOn Cash Management can integrate your Salesforce org with payment service providers in order to exchange payment information – namely, to provide your buyers the option to pay their purchases (represented as entries) via the payment page.

For details, see Integrating Payment Provider.

PSP Workflow

pay_app_psp_process

In broad strokes, payment requests are processed as follows:

(1) JustOn Cash Management prepares the payment page, encrypting the relevant entries, and publishes it to the buyer.

(2) The buyer selects a payment provider/payment method and releases the payment.

(3) The payment provider captures the payment amount in the buyer's bank.

(4) The buyer's bank transfers the captured amount to the payment provider. Subsequently, the payment provider passes the amount to the merchant's bank.

Payment Page

JustOn Cash Management includes a payment page. It provides your buyers the option to pay their purchases (represented as entries) via integrated payment service providers.

In order to invite your buyers to pay, you publish a link to your payment page. This payment link looks like

https://payment.juston.cloud/pay/:link-id/to/:tenant

where :link-id encodes the relevant entries and :tenant represents your organization.

For details, see Configuring Payment Page.

Text Customization

Depending on your requirements, you can modify or translate the texts to be displayed on the payment page. To this end, JustOn Cash Management provides the custom Salesforce object Payment Page Configuration.

Payment page configurations hold customized texts or translations for payment page texts. Once payment page configuration records are available, JustOn Cash Management retrieves the texts when loading the payment page.

Additional Pages

Your business may require to publish payment-relevant information that does not "fit" in the text components of the payment page. To support this, you create additional custom pages that are linked with the payment page. You can use this, for example, to attach your terms and conditions.

JustOn Cash Management implements support for custom pages using the Salesforce object CMS Page. Once CMS Page records are available and set Active, JustOn Cash Management produces a list of links to these custom pages in the payment page footer when loading the payment page.

Clicking a link opens the page in a modal window. Closing this window returns the user to the payment page, ready to continue the payment process.

Connected Bank Account

JustOn Cash Management directly integrates Salesforce CRM with European banks. Using the secure, EBICS-compliant connection, businesses can directly retrieve and upload relevant payment information.

Prior to using the banking connection of JustOn Cash Management, your business must enter into a (usually chargeable) contract on the intended data access with your bank. From a technical perspective, you subscribe to an EBICS-compliant service for exchanging payment information. Hence you may be referred to as the subscriber, with your bank as the other contract party.

For details, see Initializing Banking Operations. In addition, consider the banking-related specifics and conditions summarized in Banking Preconditions.

Banking Workflow

pay_app_ebics_process

In a rough outline, payment orders are processed as follows:

(1) JustOn Cash Management prepares the SEPA payment orders and encrypts the data packages.

(2) Under the EBICS signature class T, it then uploads the data to the bank, where the orders are queued.

If you have set up an amount limit for the technical user, preparing and uploading payment orders will be subject to this limit.

(3) An authorized user (EBICS signature class E or A/B) monitors the queue and releases the orders.

These operations are not controlled using JustOn Cash Management. The authorized representatives must use an appropriate third-party banking software or mobile application.

Important Concepts

Important concepts related to EBICS-compliant banking operations include

Bank access
See the bank access as a configuration "bracket" around bank accounts. It holds the credentials and parameters for accessing one or more bank accounts (as agreed with your bank).
Public bank key
Your bank publishes the public bank key – a string to be used by your JustOn Cash Management instance to decode and encode the encrypted communication. You must validate it as part of the subscriber confirmation before using the bank access.
Public subscriber key
Your JustOn Cash Management instance publishes your public subscriber key. This string is to be used by your bank to decode and encode the encrypted communication. Your bank must validate it as part of the subscriber initialization.
About EBICS

The Electronic Banking Internet Communication Standard (EBICS) is a transmission protocol for sending payment information between clients and banks as well as between banks over the Internet. It uses established standards for securely transmitting encrypted data. For details, see EBICS.

JustOn Cash Management supports EBICS 2.5 and EBICS 3.0. EBICS 2.5 is used with German banks only. EBICS 3.0 has introduced standardized Business Transaction Formats (BTF), which allow for working with German and other European banks – including French, Swiss and Austrian banks.

About SEPA Direct Debit

The European Payments Council (EPC) has established the single euro payments area (SEPA) to standardize cashless euro payments across Europe. It defines, among others, SEPA Direct Debit schemes (SDD): one primarily designed for B2C businesses (SDD Core), and one exclusively for B2B businesses (SDD B2B). The two schemes set common rules for transferring money from a debtor to a creditor, but vary in details (see SEPA Direct Debit).

SEPA Direct Debit is centered around a mandate, which allows the creditor to prove their request for collecting money. The collection is initiated by the creditor, submitting the order to their bank. The order includes information like mandate ID, amount, collection date and debtor IBAN. The bank then executes the order, withdrawing the money from the debtor's account and putting it to the creditor's account.

The common rules include:

  • The mandate is signed by the debtor before the first transaction (typically 14 days before the first collection).
  • The mandate allows one-off or recurrent collections and can be revoked by the debtor at any time.
  • The due date of a collection must not be more than 14 days in the future.

Depending on the scheme (Core or B2B), various timeframes and rules apply for the debtor to object to the money transfer and to order a reverse transaction.

The SEPA Direct Debit Core scheme is mandatory for transactions with consumers (B2C) and optional for transactions with businesses (B2B). Under SDD Core, a debtor can request a refund ("no-questions-asked") within eight weeks of the collection date. In case of an unauthorized transaction – which must be proven –, a debtor can ask for a refund within 13 months of the collection date.

The SEPA Direct Debit B2B scheme is exclusively for businesses. Under SDD B2B, the debtor is not entitled to obtain a refund for an authorized transaction. The debtor's bank, however, may still return a transaction under certain circumstances within three days. To ensure that a transaction is authorized under SDD B2B, the debtor's bank must check whether there is a valid mandate before executing the collection.