Skip to content

Payment Provider Integration

The JustOn Self-Service Extension includes a payment page. Use this page to provide your users the option to complete their checkout process, directly paying for their purchases. To this end, the JustOn Self-Service Extension can integrate with payment service providers.

Info

To set up the payment page as part of the JustOn Self-Service Extension, follow the instructions given in Site Setup and Access Settings.

Future Payments

Depending on the payment provider you use, the JustOn Self-Service Extension can expose the Future Payments option on the payment page. Future payments make use of provider-specific means to pre-authorize and execute recurring charges (or other subsequent payments) without the need to repeatedly prompt users for card or account numbers.

With the future payments feature enabled, JustOn creates an account-specific Payment Instrument record, which holds the corresponding credit card or bank account information. Based on the saved payment instruments, JustOn can then execute payment runs in order to automatically collect pre-authorized payments. For details, see Scheduling Payment Collection.

Info

Currently, Payeezy and Stripe support future payments.

Payment Notification

In the following cases, JustOn sends email notifications about failed payments:

  • A payment transaction with a long processing time has finally failed, like, for example, SEPA Direct Debit via Stripe, which may take 3-5 days
  • A future payment has failed three times

The email notification makes use of the specific template detail Payment Notification. In addition, the JustOn Self-Service Extension provides payment-specific build-in placeholders for the payment notification.

Placeholder Description
[message] The error message.
[amount] The payment amount.
[currency] The payment currency.
[bank_message] Additional message from the bank.
[gateway_message] Additional error information (Payeezy)
[cardholder] Name of the credit card holder
[expiration_date] Expiration date of the credit card
[type] Credit card type, like 'Visa'
[pan] Masked PAN of the credit card
[transaction_status] Additional error information
[validation_status] Card validation status
[risk_level] Riskiness of the payment (Stripe)
[country] Two-letter ISO code representing the country of the card (Stripe).

Info

Most placeholders are filled with information provided by the bank. The availability, meaning and contents of the placeholders depends on the payment provider and payment method.

Provider-Specific Integration

Depending on the payment provider you use, you must specifically configure the account access. To this end, the JustOn Self-Service Extension provides the Payment Provider Setup page.

The setup page is divided into two sections:

  • The first section lists the existing configurations and lets you disable/enable or delete them.
  • The second section allows you to add a new configuration.

Info

By default, you can create one payment configuration per tenant and payment provider, except for

  • Stripe: Allows for specifying individual payment configurations per payment method for the same tenant
  • Context-specific payment configurations: Allows for creating multiple invoice-specific payment configurations, irrespective of specified tenants or payment methods per payment provider. If enabled, the distinction is made based on the (unique) configuration name.

For details about individual payment provider integrations, see

PayPal
Payeezy
CyberSource
Stripe

Note

Some payment methods, like credit card, are supported by multiple payment providers. When setting up the payment configurations, you must make sure that a payment method is not available multiple times at the same time, like credit card payment via Payeezy and Cybersource.

You can, however, specify different tenants for the two payment configurations, like using CyberSource for Tenant A and Payeezy for Tenant B, and then enable credit card payments accordingly.

Context-Specific Payment Configuration

Usually, the tenant setting of your payment provider configuration determines for which invoices the configuration and hence, the specified payment method is available. Your business may, however, require specific payment providers or payment methods for for individual contexts, like accounts, opportunities, subscriptions or other source objects based on which you create invoices. To this end, you

  • Create the payment configurations as required (see Provider-Specific Integration), and
  • Specify the intended configuration on the account, opportunity, subscription or other source object, and have it set on the invoice.

To allow setting a specific payment configuration on the account or invoice:

  1. Depending on your use case, create the following field on the Account, Opportunity, Subscription or other source object.

    API Name Data Type Description
    PaymentProviderOverride Text Specifies the name of the payment configuration to be used.

    For details about creating fields, see Managing Object Fields.

  2. Create the following formula field on the Invoice object.

    API Name Data Type Description
    PaymentProviderOverride Formula (Text) Retrieves the specified payment configuration from the related object.

    Depending on your use case, the formula must specify the source field. If you have created, for example, PaymentProviderOverride on the Account object, insert this field as the formula, like:

    ONB2__Account__r.PaymentProviderOverride__c
    

You can now set the name of the intended provider configuration on your account, opportunity, subscription or other source object records, irrespective of the tenant specified in the configuration.

Info

The payment page can display the configured payment methods of multiple payment providers. Think of the following example: You want to provide a specific account the option to pay via PayPal and credit card via CyberSource. To this end:

  • You create two payment configurations with the same name: one for PayPal, and a second for CyberSource.
  • You specify the configuration name in the PaymentProviderOverride field on the intended account record.

Based on the settings, the payment page includes links to the two payment methods.

Note

For the account-specific or invoice-specific payment configuration to work as intended, you must enable Read access to the PaymentProviderOverride field on the invoice for the site guest user (see Configuring Additional Permissions for Payment Provider Integration).