This SDK does not have any support for Svea Checkout. There's technical documentation available for Svea Checkout here: https://checkoutapi.svea.com/docs/html/version-1.htm
The WebpayConnection and WebpayAdmin classes make up the Svea API. Together they provide unified entrypoints to the various Svea web services. The API also encompass the support classes IConfigurationProvider, SveaResponse and Item, as well as various constant container classes and support classes.
The WebpayConnection class methods contains the functions needed to create orders and perform payment requests using Svea payment methods. It contains methods to define order contents, send order requests, as well as support methods needed to do this.
The WebPayAdmin class methods are used to administrate orders after they have been accepted by Svea. It includes functions to update, deliver, cancel and credit orders et.al. Note! This entrypoint is under construction and all functions not yet implemented.
To build the dll file, load up the project in Visual studio. Choose 'Release' as your solution configuration and press F6. (The solution is compatible and will compile properly with .NET Framework 4.0 and higher.)
This will build the dll and place it in bin/release sub-folder of the project.
The Configuration needed to be set differs of how many different payment methods and countries you have in the same installation. The authorization values are recieved from Svea Ekonomi when creating an account. If no configuration is created, use SveaConfig.GetDefaultConfig().
To configure Svea authorization: Create a class (eg. one for testing values, one for production) that implements the IConfigurationProvider Interface. Let the implemented methods return the authorization values asked for. Later when starting a WebpayConnection action in your integration file, put an instance of your class as parameter to the constructor.
NOTE: This solution may change in future updates!
Step 1:
using Webpay.Integration.CSharp.Config;
using Webpay.Integration.CSharp.Util.Constant;
namespace SveaWebpayIntegration
{
public class MyConfigTest : IConfigurationProvider
{
/// <summary>
/// Get the return value from your database or likewise
/// </summary>
/// <param name="type"> eg. HOSTED, INVOICE or PAYMENTPLAN</param>
/// <param name="country">country code</param>
/// <returns>user name string</returns>
public string GetUsername(PaymentType type, CountryCode country)
{
return myUserName;
}
/// <summary>
/// Get the return value from your database or likewise
/// </summary>
/// <param name="type"> eg. HOSTED, INVOICE or PAYMENTPLAN</param>
/// <param name="country">country code</param>
/// <returns>password string</returns>
public string GetPassword(PaymentType type, CountryCode country)
{
return myPassword;
}
/// <summary>
/// Get the return value from your database or likewise
/// </summary>
/// <param name="type"> eg. HOSTED, INVOICE or PAYMENTPLAN</param>
/// <param name="country">country code</param>
/// <returns>client number int</returns>
public int GetClientNumber(PaymentType type, CountryCode country)
{
return myClientNumber;
}
/// <summary>
/// Get the return value from your database or likewise
/// </summary>
/// <param name="type"> eg. HOSTED, INVOICE or PAYMENTPLAN</param>
/// <param name="country">country code</param>
/// <returns>merchant id string</returns>
public string GetMerchantId(PaymentType type, CountryCode country)
{
return myMerchantId;
}
/// <summary>
/// Get the return value from your database or likewise
/// </summary>
/// <param name="type"> eg. HOSTED, INVOICE or PAYMENTPLAN</param>
/// <param name="country">country code</param>
/// <returns>secret word string</returns>
public string GetSecretWord(PaymentType type, CountryCode country)
{
return mySecretWord;
}
/// <summary>
/// Constants for the end point url found in the class SveaConfig
/// </summary>
/// <param name="type"> eg. HOSTED, INVOICE or PAYMENTPLAN</param>
/// <returns>end point url</returns>
public string GetEndPoint(PaymentType type)
{
return type == PaymentType.HOSTED ? SveaConfig.GetTestPayPageUrl() : SveaConfig.GetTestWebserviceUrl();
}
}
}
Step 2: Put an instance of your configuration object as a parameter to the request.
//Create a class including test authorization
MyConfigTest confTest = new MyConfigTest();
//Create a class including production authorization
MyConfigProd confProd = new MyConfigProd();
//Create your CreateOrder object with selected and continue building your order. Se next steps.
private CreateOrderEuResponse response = WebpayConnection.CreateOrder(confTest);
.....
We show how to specify an order, working through the various steps and options along the way: Start by creating an order using the WebpayConnection.CreateOrder() method. Pass in your configuration and get an instance of CreateOrderBuilder in return.
CreateOrderEuResponse response = WebpayConnection.CreateOrder(myConfig)
Continue by adding values for products and other. You can add order row, fee and discount. Chose the right Item object as parameter. You can use the add functions with an Item object or a List of Item objects as parameters. See types of Item objects in examples in 4.1.2 - 4.1.5 and 4.3.1 - 4.3.2.
.AddOrderRow(Item.OrderRow(). ...)
//or
var orderRows = new List<OrderRowBuilder>();
orderRows.Add(Item.OrderRow(). ...)
...
CreateOrder.AddOrderRows(orderRows);For every new payment type implementation, you follow the steps from the beginning and chose your payment type preferred in the end: Build order -> choose payment type -> DoRequest/GetPaymentForm/PreparePayment
CreateOrderEuResponse response = WebpayConnection.CreateOrder(myConfig) //See Configuration chapt.3
//For all products and other items
.AddOrderRow(Item.OrderRow()...)
//If shipping fee
.AddFee(Item.ShippingFee()...)
//If invoice with invoice fee
.AddFee(Item.InvoiceFee()...)
//If discount or coupon with fixed amount
.AddDiscount(Item.FixedDiscount()...)
//If discount or coupon with percent discount
.AddDiscount(Item.RelativeDiscount()...)
//Individual customer values
.AddCustomerDetails(Item.IndividualCustomer()...)
//Company customer values
.AddCustomerDetails(Item.CompanyCustomer()...)
//Other values
.SetCountryCode(CountryCode.SE)
.SetOrderDate(new DateTime(2012, 12, 12))
.SetCustomerReference("ref33")
.SetClientOrderNumber("33")
.SetCurrency(Currency.SEK)
//Continue by choosing one of the following paths
//Continue as a card payment
.UsePayPageCardOnly()
...
.GetPaymentForm();
or
.PreparePayment("234.214.2.23")
//Continue as a direct bank payment
.UsePayPageDirectBankOnly()
...
.GetPaymentForm();
or
.PreparePayment("234.214.2.23")
//Continue as a PayPage payment
.UsePayPage()
...
.GetPaymentForm();
or
.PreparePayment("234.214.2.23")
//Continue as a PayPage payment
.UsePaymentMethod(PaymentMethod.DBSEBSE) //see APPENDIX for Constants
...
.GetPaymentForm()
or
.PreparePayment("234.214.2.23")
//Continue as an invoice payment
.UseInvoicePayment()
...
.DoRequest();
//Continue as a payment plan payment
.UsePaymentPlanPayment("campaigncode", false)
...
.DoRequest();If you want to prepare a payment and send a link to the user for the payment. In this case a hosted payment will be used.
The .PreparePayment()-method will return a Uri for the customer to use to complete the payment of the order.
Customer identity is required for invoice and payment plan orders. Required values varies depending on country and customer type. For SE, NO, DK and FI national id number is required. Email and ip address are desirable.
.AddCustomerDetails(Item.IndividualCustomer()
.SetNationalIdNumber("194605092222") //Required for individual customers in SE, NO, DK and FI
.SetBirthDate("19460509") //Required for individual customers in NL and DE
.SetName("Tess", "Testson") //Required for individual customers in NL and DE
.SetInitials("SB") //Required for individual customers in NL
.SetStreetAddress("Gatan", "23") //Required in NL and DE
.SetCoAddress("c/o Eriksson") //Optional
.SetZipCode("9999") //Required in NL and DE
.SetLocality("Stan") //Required in NL and DE
.SetPhoneNumber("999999")) //Optional
.SetEmail("test@svea.com") //Optional but desirable
.SetIpAddress("123.123.123") //Optional but desirable.AddCustomerDetails(Item.CompanyCustomer()
.SetNationalIdNumber("2345234") //Required for company customers in SE, NO, DK, FI
.SetVatNumber("NL2345234") //Required for NL and DE
.SetCompanyName("TestCompagniet")) //Required for Eu countries like NL and DE
.SetAddressSelector("7fd7768") //Optional. Recieved from getAddresses.SetCountryCode(CountryCode.SE) //Required
.SetCurrency(Currency.SEK) //Required for card payment, direct payment and PayPage payment.
.SetClientOrderNumber("33") //Required for card payment, direct payment, Unique String(65). Optional for Invoice and Payment plan String(32).
.SetOrderDate(new DateTime(2012, 12, 12)) //Required for synchronous payments
.SetCustomerReference("ref33") //Optional for invoice and payment plan String(32), ignored for card & direct bank orders.End the process by choosing the payment method you desire.
Invoice and payment plan will perform a synchronous payment and return an object as response.
Other payments such as card, direct bank and payments from the PayPage on the other hand are asynchronous. They will return an html form with formatted message to send from your store.
The response is then returned to the return url you have specified in function SetReturnUrl(). The response may also be sent to the url specified with SetCallbackUrl() in case the customer doesn't return to the store after the transaction has concluded at the bank/card payment page.
If you pass the xml response to an instance of SveaResponse, you will receive a formatted response object as well.
I am using the invoice and/or payment plan payment methods in my integration.
The best way is to use
.UseInvoicePayment()and.UsePaymentPlanPayment(). These payment methods are synchronous and will give you an instant response.
I am using the card and/or direct bank payment methods in my integration.
The best way if you know what specific payment you want to use, is to go direct to that specific payment, bypassing the PayPage step, by using
.UsePaymentMethod(). See APPENDIX for ConstantsYou can also use the PayPage with
.UsePayPageCardOnly()and.UsePayPageDirectBankOnly().
I am using all payment methods in my integration, and wish to let the customer select which to use.
The most effective way is to use
.UseInvoicePayment()and.UsePaymentPlanPayment()for the synchronous payments, and use the.UsePaymentMethod()for the asynchronous requests.Alternatively you can go by PayPage for the asynchronous requests by using
.UsePayPageCardOnly()and.UsePayPageDirectBankOnly().
I am using more than one payment and want them gathered on on place.
You can use the PayPage and either choose to show all your payments here or exclude or include one or more payments. Use
.UsePayPage()where you can customize your own PayPage.
Please note that using this method introduces an additional step for the customer and is not recommended.
Select a payment method to use with the CreateOrderBuilder class useXX() methods, which returns an instance of the appropriate payment request class.
Perform an invoice payment. This payment form will perform a synchronous payment and return a response. Returns CreateOrderEuResponse object. Set your store authorization here.
CreateOrderEuResponse response = WebpayConnection.CreateOrder()
.AddOrderRow(...) // required, one or more
.AddCustomerDetails(...) // required, individualCustomer or companyCustomer
.SetCountryCode(CountryCode.SE) // required
.SetOrderDate(new DateTime(2012, 12, 12)) // required
.UseInvoicePayment() // requires the above attributes in the order
.DoRequest();Perform PaymentPlanPayment. This payment form will perform a synchronous payment and return a response. Returns a CreateOrderEuResponse object. Preceded by WebPay.GetPaymentPlanParams(...). Set your store authorization here. Param: Campaign code recieved from GetPaymentPlanParams().
CreateOrderEuResponse response = WebpayConnection.CreateOrder()
.AddOrderRow(...) // required, one or more
.AddCustomerDetails(...) // required, individualCustomer or companyCustomer
.SetCountryCode(CountryCode.SE) // required
.SetOrderDate(new DateTime(2012, 12, 12)) // required
.UsePaymentPlanPayment(1234L, false) //Parameter1: campaign code recieved from getPaymentPlanParams
//Paremeter2: True if Automatic autogiro form will be sent with the first notification
.DoRequest();Select i.e. .UsePaymentMethod(PaymentMethod.SVEACARDPAY) //see APPENDIX for Constants to perform a card payment via the SveaCardPay card payment provider.
PaymentForm form = WebpayConnection.CreateOrder()
.AddOrderRow(...) //required
.SetCountryCode(CountryCode.SE) // required
.SetClientOrderNumber("33")
.SetOrderDate(new DateTime(2012, 12, 12))
.UsePaymentMethod(PaymentMethod.SVEACARDPAY)
.SetReturnUrl("http://myurl.se") //Required
.SetCallbackUrl("http://myurl.se") //Optional
.SetCancelUrl("http://myurl.se") //Optional
.GetPaymentForm();
.SetReturnUrl() When a hosted payment transaction completes (regardless of outcome, i.e. accepted or denied), the payment service will answer with a response xml message sent to the return url specified.
.SetCallbackUrl() In case the hosted payment transaction completes, the payment service will always send a request to the callback url as a fallback, if specified. This is useful if the user closes the browser before getting redirected back to the shop.
.SetCancelUrl() In case the hosted payment service is cancelled by the user, the payment service will redirect back to the cancel url. Unless a return url is specified, no cancel button will be presented at the payment service.
A recurring card payment uses the same logic as a normal card payment except that you need to a subscriptionType using .SetSubscriptionType()
PaymentForm form = WebpayConnection.CreateOrder()
.AddOrderRow(...)
.SetCountryCode(CountryCode.SE)
.SetClientOrderNumber("33")
.SetCurrency("SEK")
.SetOrderDate(new DateTime(2016, 12, 24))
.UsePaymentMethod(PaymentMethod.SVEACARDPAY)
.SetSubscriptionType(subscriptionType)
.SetReturnUrl("http://myurl.se")
.GetPaymentForm();
There are four different subscription types:
RECURRING*
RECURRINGCAPTURE
ONECLICK*
ONECLICKCAPTURESubscription types marked with a * is only possible to use if the merchant has a scandinavian acquirer.
RECURRING and RECURRINGCAPTURE should be used if no action is required by the card holder, for example if the customer should be charged every month.
ONECLICK and ONECLICKCAPTURE should be used if the card holder is required to make an action each time the card should be charged such as refilling a virtual coin pouch used in games or other services.
RECURRINGCAPTURE and ONECLICKCAPTURE should be used if the merchant wants to capture the initial transaction which results in money being charged.
RECURRING and ONECLICK should be used if you dont want to capture the initial transaction, in this case the money is reserved for a few days and then will be returned unless a "recur" is made(explained below).
After using the method above you will get a subscriptionId in you response which you will use in order to make recur calls.
Subscriptions can be automaticlly charged, log in to the payment gateway to configure this otherwise use the method below to charge the card manually.
A subscription is valid for 12 months and after that you will need to renew the subscription.
By sending in the customerReference, subscriptionId, currency and amount you will successfully charge money from a existing subscription.
var hostedActionRequest = new HostedAdmin(SveaConfig.GetDefaultConfig(), CountryCode.SE)
.Recur(new Recur(
customerRefNo: 10000001,
subscriptionId: 123123123,
currency: "SEK",
amount: 10000,
vat: 2500
));
HostedAdminRequest hostedAdminRequest = hostedActionRequest.PrepareRequest();
var hostedAdminResponse = hostedActionRequest.DoRequest<HostedAdminResponse>();If the call was successful a transaction is made in the payment gateway.
To cancel a subscription you need to call .cancelRecurSubscription() with the subscriptionId.
var hostedActionRequest = new HostedAdmin(SveaConfig.GetDefaultConfig(), CountryCode.SE)
.CancelRecurSubscription(new CancelRecurSubscription(
subscriptionId: "12341234"
));
var hostedAdminRequest = hostedActionRequest.PrepareRequest();
var hostedAdminResponse = hostedActionRequest.DoRequest<HostedAdminResponse>();The payment gateway will respond with statuscode 0 indicating a success.
Select i.e. .UsePaymentMethod(PaymentMethod.NORDEASE) //see APPENDIX for Constants to perform a bank payment redirected direct to the selected bank landing page.
PaymentForm form = WebpayConnection.CreateOrder()
.AddOrderRow(...) //required
.SetCountryCode(CountryCode.SE) // required
.SetClientOrderNumber("33")
.SetOrderDate(new DateTime(2012, 12, 12))
.UsePaymentMethod(PaymentMethod.NORDEASE)
.SetReturnUrl("http://myurl.se") //Required
.SetCallbackUrl("http://myurl.se") //Optional
.SetCancelUrl("http://myurl.se") //Optional
.SetReturnUrl() When a hosted payment transaction completes (regardless of outcome, i.e. accepted or denied), the payment service will answer with a response xml message sent to the return url specified.
.SetCallbackUrl() In case the hosted payment transaction completes, the payment service will always send a request to the callback url as a fallback, if specified. This is useful if the user closes the browser before getting redirected back to the shop.
.SetCancelUrl() In case the hosted payment service is cancelled by the user, the payment service will redirect back to the cancel url. Unless a return url is specified, no cancel button will be presented at the payment service.
PayPage with all available payments. You can also custom the PayPage by using one of the methods for PayPagePayments: SetPaymentMethod, IncludePaymentMethod, ExcludeCardPaymentMethod or ExcludeDirectPaymentMethod.
PaymentForm form = WebpayConnection.CreateOrder()
.AddOrderRow(...) //required
.SetCountryCode(CountryCode.SE) // required
.SetClientOrderNumber("33")
.SetOrderDate(new DateTime(2012, 12, 12))
.UsePayPage()
.SetReturnUrl("http://myurl.se") //Required
.SetCallbackUrl("http://myurl.se") //Optional
.SetCancelUrl("http://myurl.se") //Optional
.SetReturnUrl() When a hosted payment transaction completes (regardless of outcome, i.e. accepted or denied), the payment service will answer with a response xml message sent to the return url specified.
.SetCallbackUrl() In case the hosted payment transaction completes, the payment service will always send a request to the callback url as a fallback, if specified. This is useful if the user closes the browser before getting redirected back to the shop.
.SetCancelUrl() In case the hosted payment service is cancelled by the user, the payment service will redirect back to the cancel url. Unless a return url is specified, no cancel button will be presented at the payment service.
Optional if you want to exlude specific payment methods for PayPage.
.UsePayPage()
.SetReturnUrl("http://myurl.se") //Required
.SetCancelUrl("http://myurl.se") //Optional
.ExcludePaymentMethods(new List<PaymentMethod> //Optional
{
PaymentMethod.SEBSE,
PaymentMethod.INVOICE
})
.GetPaymentForm();Optional if you want to include specific payment methods for PayPage.
.UsePayPage()
.SetReturnUrl("http://myurl.se") //Required
.IncludePaymentMethod(new List<PaymentMethod> //Optional
{
PaymentMethod.SEBSE,
PaymentMethod.INVOICE
})
.GetPaymentForm();Optional if you want to exclude all card payment methods from PayPage.
.UsePayPage()
.SetReturnUrl("http://myurl.se") //Required
.ExcludeCardPaymentMethod() //Optional
.GetPaymentForm();Optional if you want to exclude all direct bank payments methods from PayPage.
.UsePayPage()
.SetReturnUrl("http://myurl.se") //Required
.ExcludeDirectPaymentMethod() //Optional
.GetPaymentForm();Build order and recieve a PaymentForm object. Send the PaymentForm parameters: merchantid, xmlMessageBase64 and mac by POST with url. The PaymentForm object also contains a complete html form as string and the html form element as array.
<form name="paymentForm" id="paymentForm" method="post" action=" + url +">
<input type="hidden" name="merchantid" value=" + merchantId + " />
<input type="hidden" name="message" value=" + xmlMessageBase64 + " />
<input type="hidden" name="mac" value=" + mac + "/>
<noscript><p>Javascript is inactivated.</p></noscript>
<input type="submit" name="submit" value="Submit" />
</form>The values of xmlMessageBase64, merchantid and mac are to be sent as xml to SveaWebPay. Function GetPaymentForm() returns object type PaymentForm with accessible members:
| Value | Returns | Description |
|---|---|---|
| GetXmlMessageBase64() | string | Payment information in XML-format, Base64 encoded. |
| GetXmlMessage() | string | Payment information in XML-format. |
| GetMerchantId() | string | Authorization |
| GetSecretWord() | string | Authorization |
| GetMacSha512() | string | Message authentication code. |
| GetUrl() | string | Url to preselected server, test or production. |
| GetCompleteForm() | string | A complete Html form with method= "post" with submit button to include in your code. |
| GetFormHtmlFields() | Dictionary<string, string> | Map with html tags as keys with of Html form fields to include. |
The response will be returned as http GET or POST to the returnUrl and the callbackUrl.
The WebPayItem class provides entrypoint methods to the different row items that make up an order, as well as the customer identity information items.
An order must contain one or more order rows. You may add invoice fees, shipping fees and discounts to an order.
For relative discounts, or fixed discounts specified using only setAmountIncVat() or only setAmountExVat() there may be several discount rows added, should the order include more than one different vat rate. It is not recommended to specify more than one relative discount row per order, or more than one fixed discount specified using only setAmountIncVat() or only setAmountExVat().
All products and other items. It?s required to have a minimum of one order row. The price can be set in a combination by using a minimum of two out of three functions: SetAmountExVat(), SetAmountIncVat() and SetVatPercent().
.AddOrderRow(Item.OrderRow()
.SetQuantity(2) //Required
.SetAmountExVat(100.00M) //Optional, see info above
.SetAmountIncVat(125.00M) //Optional, see info above
.SetVatPercent(25.00M) //Optional, see info above
.SetArticleNumber("1") //Optional
.SetDescription("Specification") //Optional
.SetName("Prod") //Optional
.SetUnit("st") //Optional
.SetDiscountPercent(0)) //OptionalThe price can be set in a combination by using a minimum of two out of three functions: setAmountExVat(), setAmountIncVat()and setVatPercent().
.AddFee(Item.ShippingFee()
.SetAmountExVat(50) //Optional, see info above
.SetAmountIncVat(62.50M) //Optional, see info above
.SetVatPercent(25.00M) //Optional, see info above
.SetShippingId("33") //Optional
.SetName("shipping") //Optional
.SetDescription("Specification") //Optional
.SetUnit("st") //Optional
.SetDiscountPercent(0)) //OptionalThe price can be set in a combination by using a minimum of two out of three functions: setAmountExVat(), setAmountIncVat() and setVatPercent().
.AddFee(Item.InvoiceFee()
.SetAmountExVat(50) //Optional, see info above
.SetAmountIncVat(62.50M) //Optional, see info above
.SetVatPercent(25.00M) //Optional, see info above
.SetName("Svea fee") //Optional
.SetDescription("Fee for invoice") //Optional
.SetUnit("st") //Optional
.SetDiscountPercent(0)) //OptionalWhen discount or coupon is a fixed amount on total product amount.
.AddDiscount(Item.FixedDiscount()
.SetAmountIncVat(100.00M) //Required
.SetDiscountId("1") //Optional
.SetUnit("st") //Optional
.SetDescription("FixedDiscount") //Optional
.SetName("Fixed")) //OptionalWhen discount or coupon is a percentage on total product amount.
.AddDiscount(Item.RelativeDiscount()
.SetDiscountPercent(50) //Required
.SetDiscountId("1") //Optional
.SetUnit("st") //Optional
.SetName("Relative") //Optional
.SetDescription("RelativeDiscount")) //OptionalWhen adding individual customer information to an order.
.AddCustomerDetails(Item.IndividualCustomer()
.SetNationalIdNumber("194605092222") //Required for individual customers in SE, NO, DK and FI
.SetBirthDate("19460509") //Required for individual customers in NL and DE
.SetName("Tess", "Testson") //Required for individual customers in NL and DE
.SetInitials("SB") //Required for individual customers in NL
.SetStreetAddress("Gatan", "23") //Required in NL and DE
.SetCoAddress("c/o Eriksson") //Optional
.SetZipCode("9999") //Required in NL and DE
.SetLocality("Stan") //Required in NL and DE
.SetPhoneNumber("999999")) //Optional
.SetEmail("test@svea.com") //Optional but desirable
.SetIpAddress("123.123.123") //Optional but desirableWhen adding company customer information to an order.
.AddCustomerDetails(Item.CompanyCustomer()
.SetNationalIdNumber("2345234") //Required for company customers in SE, NO, DK, FI
.SetVatNumber("NL2345234") //Required for NL and DE
.SetCompanyName("TestCompagniet")) //Required for Eu countries like NL and DE
.SetAddressSelector("7fd7768") //Optional. Recieved from getAddressesThis is an extension of the orderRow class, used in the WebpayAdmin.QueryOrder() response and methods that adminster individual order rows.
Item.NumberedOrderRow()
//inherited functions from OrderRow
...
//numbered orderrow functions:
.SetCreditInvoiceId() //optional
.SetInvoiceId() //optional
.SetRowNumber() //required for UpdateOrderrow()
.SetStatus() //optional
The WebpayConnection class methods contains the functions needed to create orders and perform payment requests using Svea payment methods. It contains entrypoint methods used to define order contents, send order requests, as well as various support methods needed to do this.
Use WebpayConnection.CreateOrder() to create an order using invoice, payment plan, card, or direct bank payment methods.
See the CreateOrderBuilder class for more info on methods used to specify the order builder contents and chosing a payment method to use, followed by sending the request to Svea and parsing the response.
See the CreateOrderBuilder class for more info on methods used to specify the order builder contents and chosing a payment method to use, followed by sending the request to Svea and parsing the response.
Invoice and Payment plan orders will perform a synchronous payment on doRequest(), and will return a response object immediately.
Card, Direct bank, and other hosted methods accessed via PayPage are asynchronous. They provide an html form containing a formatted message to send to Svea, which in turn will send a request response to a given return url, where the response can be parsed using the SveaResponse class.
CreateOrderEuResponse response = WebpayConnection.CreateOrder(myConfig) //See Configuration chapt.3
//For all products and other items
.AddOrderRow(Item.OrderRow()...)
//If shipping fee
.AddFee(Item.ShippingFee()...)
//If invoice with invoice fee
.AddFee(Item.InvoiceFee()...)
//If discount or coupon with fixed amount
.AddDiscount(Item.FixedDiscount()...)
//If discount or coupon with percent discount
.AddDiscount(Item.RelativeDiscount()...)
//Individual customer values
.AddCustomerDetails(Item.IndividualCustomer()...)
//Company customer values
.AddCustomerDetails(Item.CompanyCustomer()...)
//Other values
.SetCountryCode(CountryCode.SE)
.SetOrderDate(new DateTime(2012, 12, 12))
//Optional, use if company wants Peppol invoice
.SetPeppolId("1234:ab1234")
.SetCustomerReference("ref33")
.SetClientOrderNumber("33")
.SetCurrency(Currency.SEK)
Use this function to retrieve campaign codes for possible payment plan options. Use prior to create payment plan payment. Returns PaymentPlanParamsResponse object. Set your store authorization here.
GetPaymentPlanParamsEuResponse response = WebpayConnection.GetPaymentPlanParams()
.SetCountryCode(CountryCode.SE) //Required
.DoRequest();Use this function to calculate the prices per month of the payment plan campaigns received from GetPaymentPlanParams. paymentPlanParams is the response object from GetPaymentPlanParams.
List<Dictionary<string, string>> pricePerMonth = WebpayConnection.PaymentPlanPricePerMonth(amount, paymentPlanParams);Returns getAddressesResponse object with an AddressSelector for the associated addresses for a specific security number. Can be used when creating an order. Only applicable for SE, NO and DK. In Norway, only getAddresses of companies is supported. Set your store authorization here.
Set order type
.SetOrderTypeInvoice() //Required if this is an invoice order
or
.SetOrderTypePaymentPlan() //Required if this is a payment plan orderCustomer type
.SetIndividual("194605092222") //Required if this is an individual customer
or
.SetCompany("companyId") //Required if this is a company customer
```csharp
GetAddressesEuResponse response = WebpayConnection.GetAddresses(myConfig) //see more about Configuration chapt.3
.SetCountryCode(CountryCode.SE) //Required
.SetOrderTypeInvoice() //Required. Used by Configurationprovider to get the right config
.SetIndividual("194605092222") //See Individual or Company
.DoRequest();Use the WebpayConnection.DeliverOrder request to deliver one Invoice order with specified orderrows and/or one complete payementplan order. Use the WebpayConnection.DeliverOrder request to confirm one Card order. You can use this function to credit an invoice order, but it is recomended to use WebpayConnection.CreditOrderrows() instead. You can use this function to partly deliver an invoice order, but it is recomended to use WebpayConnection.DeliverOrderRows() instead. If you want to deliver a complete order, or orders, it is recomended to use WebpayConnection.DeliverOrders() instead.
Paymentplan orders can not be partly delivered, and there fore no orderrows is required.
Returns DeliverOrderEuResponse object.
For invoice orders, the specified rows will automatically be matched with the rows that was sent when creating the order.
If an item is left out from the DeliverOrder request that was present in the CreateOrder request, a new invoice will be created as the order is assumed to be partially fulfilled. Any left out items should not be delivered physically, as they will not be invoiced when the DeliverOrder request is sent.
DeliverOrderBuilder request = WebpayConnection.DeliverOrder(config)
.SetOrderId() // invoice or payment plan only, required
.SetCountryCode() // required
.SetInvoiceDistributionType() // invoice only, required
.SetNumberOfCreditDays() // invoice only, optional
.AddOrderRow() // Required for invoice payments
.SetCreditInvoice() // invoice only. optional
;
// then select the corresponding request class and send request
response = request.DeliverInvoiceOrder().doRequest(); // returns DeliverOrderResponse
response = request.DeliverPaymentPlanOrder().doRequest(); // returns DeliverOrderResponse
response = request.DeliverCardOrder().doRequest(); // Confirms a card order and returns ConfirmResponse
You can add OrderRow, Fee and Discount. Choose the right Item as parameter. You can use the .Add functions with an Item or list of Items as parameters.
.AddOrderRow(Item.OrderRow(). ...)
//or
List<OrderRowBuilder> orderRows = new List<OrderRowBuilder>(); //or use another preferrable List object
orderRows.Add(Item.OrderRow(). ...)
...
DeliverOrder.AddOrderRows(orderRows);All synchronous responses are handled through SveaResponse and structured into objects. Asynchronous responses recieved after sending the values merchantid and xmlMessageBase64 to hosted solutions can also be processed through the SveaResponse class.
The response from server will be sent to the returnUrl with POST or GET. The response contains the parameters: response, merchantid and mac. Class SveaResponse will return an object structured similar to the synchronous answer.
It's highly recommended to validate the mac parameter that is contained in the response, which is done by processing the correct variables through the SveaResponse class.
Params: responseXmlBase64 - The POST or GET message Base64 encoded macToValidate - Mac provided in the POST or GET message countryCode - Your countryCode(i.e SE) SveaConfig - SveaConfig object containing merchantid and secret word
var respObject = new SveaResponse(responseXmlBase64, macToValidate, countryCode, SveaConfig);If the mac is invalid the decoded xml will contain an ErrorMessage saying "Mac validation failed." and if the validation is successful the ResultCode will be "0 (ORDER_ACCEPTED)".
If you dont want to validate the mac simply see the example below.
Params:
var respObject = new SveaResponse(responseXmlBase64);The WebpayAdmin class methods contains the functions needed to handle orders for Webservice payments as well as hosted payments. It contains entrypoint methods used to define order contents, send order requests, as well as various support methods needed to do this.
The WebpayAdmin.QueryOrder entrypoint method is used to get information about an order.
QueryOrderBuilder request = WebpayAdmin.QueryOrder(config)
.SetOrderId() // required
.SetTransactionId() // optional, card or direct bank only, alias for SetOrderId
.SetCountryCode() // required
;
// then select the corresponding request class and send request
response = request.QueryInvoiceOrder().DoRequest(); // returns AdminWS.GetOrdersResponse
response = request.QueryPaymentPlanOrder().DoRequest(); // returns AdminWS.GetOrdersResponse
response = request.QueryCardOrder().DoRequest(); // returns Hosted.Admin.Actions.QueryResponse
response = request.QueryDirectBankOrder().DoRequest(); // returns Hosted.Admin.Actions.QueryResponse
The WebpayAdmin.DeliverOrderRows entrypoint method is used to deliver individual order rows. Supports invoice and card orders.
For Invoice orders, the order row status is updated at Svea following each successful request.
For card orders, an order can only be delivered once, and any non-delivered order rows will be cancelled (i.e. the order amount will be lowered by the sum of the non-delivered order rows). A delivered card order has status CONFIRMED at Svea.
Get an order builder instance using the WebpayAdmin.DeliverOrderRows() entrypoint, then provide more information about the transaction and send the request using the DeliverOrderRowsBuilder methods:
Use SetRowToDeliver() or SetRowsToDeliver() to specify the order row(s) to deliver. The order row indexes should correspond to those returned by i.e. WebpayAdmin.QueryOrder();
For card orders, use AddNumberedOrderRow() or AddNumberedOrderRows() to pass in a copy of the original order rows. The original order rows can be retrieved using WebpayAdmin.QueryOrder; the numberedOrderRows attribute contains the serverside order rows w/indexes. Note that if a card order has been modified (i.e. rows cancelled or credited) after the initial order creation, the returned order rows will not be accurate.
DeliverOrderRowsBuilder request = WebpayAdmin.DeliverOrderRows(config)
.SetOrderId() // required
.SetTransactionId() // optional, card or direct bank only, alias for SetOrderId
.SetCountryCode() // required
.SetInvoiceDistributionType() // required for invoice only
.SetRowToDeliver() // required, index of original order rows you wish to deliver
.AddNumberedOrderRow() // required for card orders, should match original row indexes
;
// then select the corresponding request class and send request
response = request.DeliverInvoiceOrderRows().DoRequest(); // returns AdminWS.DeliverOrderRowsResponse
response = request.DeliverCardOrder().DoRequest(); // returns Hosted.Admin.Actions.ConfirmResponse
Use WebpayAdmin.DeliverOrders to deliver one or more orders of the same type without specifying order rows.
All order rows as currently held by Svea will be delivered when the request is made.
When delivered, invoice orders will return a corresponding invoice id, and payment plan orders a contract number.
These may be found in the returned DeliverOrderResult structure along with the corresponding order id. DeliverOrdersBuilder request = WebpayAdmin.DeliverOrders(config)
.SetOrderId() // optional, order id to deliver
.SetOrderIds() // optional, note that order ids must all be of the same type (invoice, part payment)
.SetCountryCode() // required
.SetInvoiceDistributionType() // required for invoice only, will apply to all invoice orders
;
// then select the corresponding request class and send request
response = request.DeliverInvoiceOrders().DoRequest(); // returns AdminWS.DeliveryResponse
response = request.DeliverPaymentPlanOrders().DoRequest(); // returns AdminWS.DeliveryResponse
The WebpayAdmin.CancelOrder() entrypoint method is used to cancel an order with Svea, that has not yet been delivered (invoice, payment plan) or confirmed (card).
Supports Invoice, Payment Plan and Card orders.
Get an instance using the WebpayAdmin.CancelOrder entrypoint, then provide more information about the order and send the request using the CancelOrderBuilder methods:
CancelOrderBuilder request = WebpayAdmin.CancelOrder(config)
.SetOrderId() // required, use SveaOrderId recieved with createOrder response
.SetTransactionId() // optional, card or direct bank only, alias for SetOrderId
.SetCountryCode() // required
;
// then select the corresponding request class and send request
response = request.CancelInvoiceOrder().DoRequest(); // returns AdminWS.CancelOrderResponse
response = request.CancelPaymentPlanOrder().DoRequest(); // returns AdminWS.CancelOrderResponse
response = request.CancelCardOrder().DoRequest(); // returns Hosted.Admin.Actions.AnnulResponse
The WebpayAdmin.CancelOrderRows() entrypoint method is used to cancel orderrows in an order before it has been delivered. The WebpayAdmin.CancelOrderRows() entrypoint method is used to lower transaction on a card order.
Supports Invoice, Payment Plan and Card orders.
Get an instance using the WebpayAdmin.CancelOrderRows entrypoint, then provide more information about the order and send the request using the CancelOrderBuilder methods:
CancelOrderRowsBuilder request = WebpayAdmin.CancelOrderRows(config)
.SetInvoiceId() // required for invoice only, use invoice number recieved with deliverOrder response
.SetTransactionId() // optional, card only, alias for SetOrderId()
.SetCountryCode() // required
.SetRowToCancel() // optional, index of original order rows you wish to deliver
.AddNumberedOrderRow() // required for card orders, should match orginal row indexes
;
// then select the corresponding request class and send request
response = request.CancelInvoiceOrderRows().DoRequest(); // returns AdminWS.CancelOrderRowsResponse
response = request.CancelPaymentPlanOrderRows().DoRequest(); // returns AdminWS.CancelOrderRowsResponse
response = request.CancelCardOrderRows().DoRequest(); // returns Hosted.Admin.Actions.LowerAmountResponse
The WebpayAdmin.CreditAmount entrypoint method is used to credit an amount in an order after it has been delivered. Supports PaymentPlan, card and direct bank. The amount is cancelled from a Payment Plan. The amount is credited from a card och bank transaction that have reached the status SUCCESS, meaning it has to be confirmed and captured.
Get an order builder instance using the WebpayAdmin.CreditAmount entrypoint, then provide more information about the transaction and send the request using the CreditAmountBuilder methods:
CreditAmountBuilder request = WebpayAdmin.CreditAmount(config)
.SetContractNumber() // required for payment plan only, use contract number recieved with deliverOrder response
.SetTransactionId() // required for card or direct bank only
.SetCountryCode() // required for payment plan only
.SetDescription() // optional for payment plan only, description to print on resulting cancellation rows
.SetAmountIncVat() // required, amount to credit
;
// then select the corresponding request class and send request
response = request.CreditPaymentPlanAmount().DoRequest(); // returns AdminWS.CancelPaymentPlanAmountResponse
response = request.CreditCardAmount().DoRequest(); // returns Hosted.Admin.Actions.CreditResponse
response = request.CreditDirectBankAmount().DoRequest(); // returns Hosted.Admin.Actions.CreditResponse
The WebpayAdmin.CreditOrderRows entrypoint method is used to credit rows in an order after it has been delivered. Supports invoice, PaymentPlan. (To credit a payment plan order, please contact Svea customer service first.)
If you wish to credit an amount not present in the original order, use addCreditOrderRow() or addCreditOrderRows() and supply a new order row for the amount to credit.
If you wish to credit an invoice or Payment Plan order row in full, you can specify the index of the order row to credit using setRowToCredit(). The corresponding order row at Svea will then be credited.
* Following the request Svea will issue a credit invoice including the original order rows specified using setRowToCredit(),
* as well as any new credit order rows specified using addCreditOrderRow().Get an order builder instance using the WebpayAdmin.CreditOrderRows entrypoint, then provide more information about the transaction and send the request using the CreditOrderRowsBuilder methods:
CreditOrderRowsBuilder request = WebpayAdmin.CreditOrderRows(config)
.SetInvoiceId() // required for invoice only, use invoice number recieved with deliverOrder response
.SetContractNumber() // required for payment plan only, use contract number recieved with deliverOrder response
.SetInvoiceDistributionType() // required for invoice only
.SetCountryCode() // required
.AddCreditOrderRow() // optional, use to specify a new credit row, i.e. for amounts not present in the original order
.SetRowToCredit() // optional, index of original order rows you wish to deliver
;
// then select the corresponding request class and send request
response = request.CreditInvoiceOrderRows().DoRequest(); // returns AdminWS.DeliveryResponse
response = request.CreditPaymentPlanOrderRows().DoRequest(); //returns AdminWS.CancelPaymentPlanRowsResponse
The WebpayAdmin.CreditOrderRows entrypoint method is used add orderrows to an order. If the new order amount exceeds the remaining amount on the order, a new credit check is made.
Supports invoice, PaymentPlan.
AddOrderRowsBuilder request = WebpayAdmin.AddOrderRows(config)
.SetOrderId() // required, use svea order number recieved in create order response
.SetCountryCode() // required
.AddOrderRow() // required, new OrderRowBuilder, replaces original order row with matching row number
;
// then select the corresponding request class and send request
response = request.AddInvoiceOrderRows().DoRequest(); // returns AdminWS.AddOrderRowsResponse
response = request.AddPaymentPlanOrderRows().DoRequest(); // returns AdminWS.AddOrderRowsResponse
The WebpayAdmin.UpdateOrder entrypoint method is used to add or change ClientOrderNumber and/or Notes.
Supports invoice, PaymentPlan.
UpdateOrderBuilder request = WebpayAdmin.UpdateOrder(config)
.SetOrderId() // required
.SetCountryCode() // required
.SetClientOrderNumber() // optional, new ClientOrderNumber field content, string w/max length of 29
.SetNotes() // optional, invoice only, new Notes field content, string w/max length of 200
;
// then select the corresponding request class and send request
response = request.UpdateInvoiceOrder().DoRequest(); // returns AdminWS.UpdateOrderResponse
response = request.UpdatePaymentPlanOrder().DoRequest(); // returns AdminWS.UpdateOrderResponse
is used to update individual order rows in non-delivered invoice and payment plan orders. The order row status of the order is updated at Svea to reflect the updated order rows. If the updated rows' order total amount exceeds the original order total amount, an error is returned by the service.
Supports invoice, PaymentPlan.
UpdateOrderRowsBuilder request = WebpayAdmin.UpdateOrderRows(config)
.SetOrderId() // required, use svea order number recieved in create order response
.SetCountryCode() // required
.AddUpdateOrderRow() // required, new NumberedOrderRowBuilder, replaces original order row with matching row number
;
// then select the corresponding request class and send request
response = request.UpdateInvoiceOrderRows().DoRequest(); // returns AdminWS.UpdateOrderRowsResponse
response = request.UpdatePaymentPlanOrderRows().DoRequest(); // returns AdminWS.UpdateOrderRowsResponse
You can validate any string to see if it's a valid peppol-ID by calling the static method "IsValidPeppolId" in the PeppolId class in the "Webpay.Integration.CSharp.Webservice.Helper" namespace
Example:
bool validationResult = PeppolId.IsValidPeppolId("1234:asdf"); // will return true
bool validationResult = PeppolId.IsValidPeppolId("1:1"); // will return falseEnumeration, used in UsePaymentMethod(PaymentMethod PaymentMethod), .UsePayPage(),
.IncludePaymentMethod(Collection
| Payment method | Description |
|---|---|
| PaymentMethod.BANKAXESS | Direct bank payment, Norway. |
| PaymentMethod.NORDEA_SE | Direct bank payment, Nordea, Sweden. |
| PaymentMethod.SEB_SE | Direct bank payment, private, SEB, Sweden. |
| PaymentMethod.SEBFTG_SE | Direct bank payment, company, SEB, Sweden. |
| PaymentMethod.SHB_SE | Direct bank payment, Handelsbanken, Sweden. |
| PaymentMethod.SWEDBANK_SE | Direct bank payment, Swedbank, Sweden. |
| PaymentMethod.KORTCERT | Card payments, Certitrade. |
| PaymentMethod.SVEACARDPAY | Card payments, Svea. |
| PaymentMethod.SVEACARDPAY_PF | Card payments, Svea w/ Payment Facilitator |
| PaymentMethod.PAYPAL | Paypal |
| PaymentMethod.SKRILL | Card payment with Dankort, Skrill. |
| PaymentMethod.INVOICE | Invoice by PayPage. |
| PaymentMethod.PAYMENTPLAN | PaymentPlan by PayPage. |
Enumeration, used in .SetCountryCode(...). Using ISO 3166-1 standard.
| CountryCode | Country |
|---|---|
| CountryCode.DE | Germany |
| CountryCode.DK | Denmark |
| CountryCode.FI | Finland |
| CountryCode.NL | Netherlands |
| CountryCode.NO | Norway |
| CountryCode.SE | Sweden |
Enumeration, used in .SetPayPageLanguage(...). Using ISO 639-1 standard.
| LanguageCode | Language name |
|---|---|
| LanguageCode.da | Danish |
| LanguageCode.de | German |
| LanguageCode.en | English |
| LanguageCode.es | Spanish |
| LanguageCode.fr | French |
| LanguageCode.fi | Finnish |
| LanguageCode.it | Italian |
| LanguageCode.nl | Dutch |
| LanguageCode.no | Norwegian |
| LanguageCode.sv | Swedish |
Enumeration, used in .SetCurrency(...). Using ISO 4217 standard.
| CurrencyCode | Currency name |
|---|---|
| Currency.DKK | Danish krone |
| Currency.EUR | Euro |
| Currency.NOK | Norwegian krone |
| Currency.SEK | Swedish krona |
Enumeration, used in .SetInvoiceDistributionType(...).
| DistributionType | Description |
|---|---|
| Post | Invoice is sent by mail |
| Invoice is sent by e-mail |