Payment Provider Settings

When creating a new payment provider, in addition to the default properties available on PaymentSettings you can define custom settings for the payment provider, similar to the AsynchronousExample payment provider and it’s AsynchronousExample PaymentSettingsBase object.

The supported property types are based off using TypeDescriptor.GetConverter and will support at minimum string/guid/int/bool/enum/uri.

The property types can also be store/language specific using the ekom custom umbraco property editors.

Settings and their order of precedence

When populating paymentsettings, custom and default, we read the properties, their types and scope (language/store) via reflection and then populate them using the following order of precedence:

assigned object property in code on a PaymentSettings or PaymentSettingsBase object, umbraco node property value and finally the appsettings configuration value.

The current store and language is read from the session context.

A working example can be viewed by running the Ekom.Site project and inspecting both the umbraco nodes and their values as well as the appsettings.json

The settings configured in appsettings.json for payment providers are nested under the following section

Ekom:Payments