Skip to main content

Webservice API Documentation

Overview​

The Svea Payments Webservice allows secure SOAP-based transactions for various payment operations.

Endpoint​

WSDL Endpoints​

Requests should be made over SOAP 1.2 using the document-literal wrapped format with a SOAP action specified.

Supported API Calls​

1. General Payment API​

2. Campaign Methods​

3. Customer Address Retrieval​

Integration and Support​

For test accounts or further integration questions, please contact Svea Payments via email:

📧 support-payments@svea.com

Order Rows​

For individual customers, we highly recommend that you:

  • Add order rows where the amount of PricePerUnit and DiscountAmount (if any) is including VAT, together with their appropriate flags PriceIncludingVat and DiscountAmountIncludingVat set to true.

For company customers we highly recommend that you do the opposite:

  • Add order rows where the amount of PricePerUnit and DiscountAmount (if any) is excluding VAT, together with their appropriate flags PriceIncludingVat and DiscountAmountIncludingVat set to false.

Disclaimer:
This documentation is subject to continuous updates. If you have any questions, please contact support-payments@svea.com.

Order Creation Flowcharts​

Create and deliver order​

The following chart illustrates an example flow for creating and delivering an order. This is the standard flow that all new clients of Svea Payment will follow.

Create and close order​

The following chart illustrates an example flow for creating and closing an order. This is the standard flow that all new clients of Svea Payment will follow.

Methods

Abbreviations and Types used in this documentation​

  • U: Unique
  • R: Required

Types​

  • Text: Any plain text. Remember that certain characters (like &) have special meaning in XML and need to be either escaped or encased in a CDATA block.
  • Integer: Number without decimals. Like 10, 42, -92.
  • Long: A longer integer.
  • Decimal: Decimal number. Like 10.65 or -43.34.
    • When there is a parenthesis in the decimal declaration like Decimal (11,2), it means that the field supports 11 significant numbers and 2 decimals.
  • The number following text fields like Text (2) means that the maximum length for this field is 2.

Common to all requests​

BasicRequest​

FieldRTypeDescription
Auth*ClientAuthInfoLog in information

Common to all responses​

BasicResponse​

FieldRTypeDescription
Accepted*BooleanTrue if the request is accepted, otherwise false.
ErrorMessage-StringWhen Accepted is false, ErrorMessage may contain a message describing the reason for rejection.
Last updated on