Umbraco.Forms.Integrations.Commerce.emerchantpay
2.0.3
Prefix Reserved
See the version list below for details.
dotnet add package Umbraco.Forms.Integrations.Commerce.emerchantpay --version 2.0.3
NuGet\Install-Package Umbraco.Forms.Integrations.Commerce.emerchantpay -Version 2.0.3
<PackageReference Include="Umbraco.Forms.Integrations.Commerce.emerchantpay" Version="2.0.3" />
paket add Umbraco.Forms.Integrations.Commerce.emerchantpay --version 2.0.3
#r "nuget: Umbraco.Forms.Integrations.Commerce.emerchantpay, 2.0.3"
// Install Umbraco.Forms.Integrations.Commerce.emerchantpay as a Cake Addin #addin nuget:?package=Umbraco.Forms.Integrations.Commerce.emerchantpay&version=2.0.3 // Install Umbraco.Forms.Integrations.Commerce.emerchantpay as a Cake Tool #tool nuget:?package=Umbraco.Forms.Integrations.Commerce.emerchantpay&version=2.0.3
Umbraco.Forms.Integrations.Commerce.emerchantpay
This integration provides a custom workflow for handling online payments using a hosted payment page provided by emerchantpay.
Prerequisites
Required minimum versions of Umbraco CMS:
- CMS: 10.1.0
- Forms: 10.1.0
How To Use
To get started with emerchantpay a merchant would need to be onboarded in order to get a merchant ID and obtain the keys required by the integration.
To begin the onboarding process an obtain the merchant account, you would need to fill out this form. Afterwards, a member of the emerchantpay team will reach out to you.
Customer journey map
A merchant getting started with emerchantpay and Umbraco will need to make sure that they have an emerchantpay merchant account enabled and then cover these steps:
- Package Installation
- Site Settings
- Workflow Setup
Authentication
All requests to emerchantpay API are authenticated by providing the merchant's username and password.
If the configuration is incomplete, the user will receive an error message.
Configuration
The emerchantpay API endpoints accept and return XML data. When the form is submitted, two batches of payload data are exchanged: one for handling consumer information and the second one for creating the payment.
A consumer has the following available properties that can be mapped against form fields:
- FirstName
- LastName
- Address1
- Address2
- ZipCode
- City
- State
- Country
- Phone
The below configuration - consisting of authentication settings, merchant specific details and customizable payment fields - is required. Some configuration items are stored as an array of strings or a dictionary, and parsed using a specific service.
{
"Umbraco": {
"Forms": {
"Integrations": {
"Commerce": {
"Emerchantpay": {
"Settings": {
"GatewayBaseUrl": "https://staging.gate.emerchantpay.net/",
"WpfUrl": "https://staging.wpf.emerchantpay.net/wpf/",
"Username": "[your_merchant_username]",
"Password": "[your_merchant_password]",
"UmbracoBaseUrl": "[your_website_url]",
"Supplier": "Umbraco",
"Usage": "Payment Gateway using Umbraco Forms",
"Currencies": {
"USD": "US Dollar",
"EUR": "Euro",
"GBP": "British Pound",
"DKK": "Danish Krone"
},
"TransactionTypes": [ "authorize", "sale" ],
"MappingFields": [ "Email", "FirstName", "LastName" ]
}
}
}
}
}
}
}
Working with the Umbraco Forms - emerchantpay integration
To use it you will need to attach the emerchantpay Gateway to a form and map the Amount, Currency, Number of Items, Record Status, Record Payment Unique ID and Consumer Details with matching form fields, then configure the event handlers for payment sucessfully processed, failed or cancelled.
When a form is submitted on the website, the workflow will execute and based on it's settings, two data payloads will be sent to emerchantpay for creating or retrieving the details of a consumer, and for creating a payment. The response for the second request will provide the URL for the hosted payment page, and the user will the redirected there.
On completing the payment the emerchantpay API will return the user to the page provided in matching event handler of the worklow.
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
-
net6.0
- Umbraco.Cms.Web.BackOffice (>= 10.1.0)
- Umbraco.Cms.Web.Website (>= 10.1.0)
- Umbraco.Forms (>= 10.1.0)
- Umbraco.Forms.Core (>= 10.1.0)
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.