Download the PHP package sveaekonomi/checkout without Composer

PHP Checkout library for Svea Checkout

Index

• 1. Setup
• 2. General information
• 3. Create order
• 4. Get order
• 5. Update order
• 6. Create recurring order
• 7. Get recurring order
• 8. Response
• 9. Additional requests
• 10. Data structures
• 11. HttpStatusCodes
• 12. Order administration
• 13. Javascript API

  Introduction

  The checkout offers a complete solution with a variety of payment methods. The payment methods that are currently available in the checkout are invoice, payment plan, account credit, card payments and payment by bank.

The checkout supports both B2C and B2B payments, fast customer identification and caches customers behaviour.

This library provides entrypoints to integrate the checkout into your platform and to administrate checkout orders.

Test credentials

You can find credentials that can be used in the stage environment without signing an contract with Svea Bank here

The example files also contain merchant credentials which can be used in the stage environment.

1. Setup

1.1 Installing with Composer

Execute the following line in your command line interface:

or add the following to your composer.json:

and run command composer update in your CLI

1.2 Install without composer

You can also download the library and upload it onto your server.

2. General information

2.1 Creating a Connector

You have to use a connector object as parameter when creating a CheckoutClient or a CheckoutAdminClient-object which is used to create API requests.

The connector defines what credentials should be used and which environment should be used.

Parameters for creating Connector are: checkoutMerchantId, checkoutSecret and base API url(environment).

2.2 CheckoutClient

The CheckoutClient class contains four methods which can be used to:

• Create order - Creates a Svea Checkout order
• Update order - Updates an existing Svea Checkout order
• Get order - Gets order data from an existing order
• Get payment plan campaigns - Fetches campaigns which can for example be used to display price per month on product page

To ensure that a snippet always is displayed to the end-user, we recommend using the following flow in your platform:

2.3 CheckoutAdminClient

The CheckoutAdminClient class contains methods which are used to administrate orders which have been creating using the CheckoutClient class.

Orders can only be administrated if CheckoutOrderStatus is "FINAL", any other status indicates that the order has not been finalized by the end-customer.

In order to perform an action on an order, the order needs to have an actions are available and then use a corresponding method.

For example, if you want to credit an order you first have to use Credit amount to credit the order.

Some actions may not be available on certain order types, but a good integration doesn't check order type but rather which actions are available for use.

The available methods are:

• Get order - Returns order data from Payment Admin, contains other information than the method in CheckoutClient
• Get task - Returns the status of a previously performed operation
• Deliver order - Creates a delivery on a checkout order(sends invoice to end-customer etc.)
• Deliver order with lower amount - Creates a delivery on a checkout order(sends invoice to end-customer etc.) with a lower amount canceling the remaining amount
• Cancel order - Cancels an order
• Cancel order amount - Removes a specified amount from an order
• Cancel order row - Removes order rows from an order
• Credit order rows - Credits order rows on a delivered order
• Credit new order row - Creates a new order row with a credited amount
• Credit order rows with fee - Credits order rows on a delivered order and adds a fee
• Credit amount - Credits a specified amount
• Add order row - Adds an order row to the order
• Update order row - Updates an existing order row
• Replace order rows - Replaces all order rows on an order with new order rows

3. Create order

To create a new order, you'll need to instantiate an object of \Svea\Checkout\CheckoutClient and pass a Connector as an parameter.

You can then use the method "create" in the object, pass the data below into the method. See example below.

The response will contain all order data along with a snippet which contains the iframe which needs to be rendered to the end-user.

Create order example:

See full example

4. Get Order

To fetch an existing order, you'll need to instantiate an object of \Svea\Checkout\CheckoutClient and pass a Connector as an parameter.

You can then use the method "get" in the object, pass the data below into the method. See example below.

The response contains the order information and the along with the GUI which can be used to render the iframe once again.

See full example

5. Update Order

To update an existing order, you'll need to instantiate an object of \Svea\Checkout\CheckoutClient and pass a Connector as an parameter.

The method returns the order information and the updated Gui needed to display the iframe for Svea Checkout. The previously displayed iframe should be replaced by the iframe in the response received when updating the order unless using the Javascript API.

Updating an order is only possible while the CheckoutOrderStatus is "Created", see CheckoutOrderStatus.

This method can be combined with the Javascript API, if the iframe is disabled using the JS API and the order is updated while the it's disabled the iframe will be updated once it's enabled again. This removes the requirement of replacing the iframe once the order is updated.

See full example

6. Create recurring order

In order to create a recurring order the feature must be enable on your merchant. Contact Svea if you'd like to enable this feature.

To create a recurring order, you'll need to instantiate an object of \Svea\Checkout\CheckoutClient and pass a Connector as an parameter. In the data you'll have to specify the recurringToken which is returned when the order is finalized.

This uses the checkoutApi and will create a new order that you later can see in PaymentAdmin.

Example:

7. Get recurring order

In order to get a recurring order you need to pass the token used to create the order as well as the orderId. Please note that this is only for orders previously created with the get order method.

Example:

8. Response

The response contains information about the order such as Cart, Status, PaymentType and much more.

Sample response

The checkout GUI contains the Snippet and the Layout. The Snippet contains the Html and JavaScript that you implement on your page where you want to display the iframe for Svea checkout. The Layout is a String defining the orientation of the customers screen.

9. Additional requests

9.1 GetAvailablePartPaymentCampaigns

GetAvailablePartPaymentCampaigns can be used to fetch the details of all the campaigns that are available on the merchant

The information can be used to for example display information about how much it will cost to pay for a certain product or products on the actual product page.

See example

Example Request:

Executing the code above will return an array with 8.11 CampaignCodeInfo

Example response:

The information should be stored in a database for fast access instead of sending requests on demand.

Calculation formulas

Calculating price per month:

Using the second campaign with a product price of 1500kr in the example above will result in: (0 + (ceil(1500 0.092586652785396) + 29 ) 12) / 12 = (0 + (139 + 29) * 12 ) / 12 = 168kr

Calculating total amount to pay:

Using the second campaign with a product price of 150kr in the example above will result in: 0 + (150 0.092586652785396 + 29 ) 12 = 514.655975 round upwards to closest whole number -> 515kr

!!! NOTE !!!

If you are a finnish merchant you have to display ALL the values described here to be compliant with finnish laws.

10. Data structures

10.1 MerchantSettings

10.2 Items

10.3 OrderRow

10.4 PresetValue

List of presetvalue typenames

10.5 Gui

10.6 Customer

10.7 Address

10.8 CheckoutOrderStatus

The order can only be considered “ready to send to customer” when the CheckoutOrderStatus is Final. No other status can guarantee payment.

10.9 Locale

10.10 PaymentType

Directbanks:

10.11 CampaignCodeInfo

10.12 IdentityFlags

10.13 CheckoutValidationCallbackResponse

If a CheckoutValidationCallbackUri is set on an order when it's created, Svea will send a HTTP GET request to the specified URI when a customer clicks on "Confirm Order".

The response should have HTTP status 200, indicating a successful request. The response should contain the required parameters below. Encode the response in JSON before responding.

11. HttpStatusCodes

If the returned ResultCode is not present in the above tables please contact Svea Ekonomi for further information.

12. Order administration

See full examples

Errors

If any action is unsuccessful or there is any other error, library will throw exception

Possible Exceptions \Svea\Checkout\Exception\SveaInputValidationException - If any of the input fields is invalid or missing.

\Svea\Checkout\Exception\SveaApiException - If there is some problem with API connection or some error occurred with data validation on the API side.

\Svea\Checkout\Exception\SveaConnectorException - will be returned if some of fields merchantId, sharedSecret or baseUrl is missing.

\Exception - For any other error

12.1 Get order

This method is used to get the entire order with all its relevant information. Including its deliveries, rows, credits and addresses.

Parameters

Response

12.2 Get task

A task will explain the status of a previously performed operation. When finished it will point towards the new resource with the Location.

Parameters

Response

12.3 Deliver order

Creates a delivery on a checkout order. Assuming the order got the CanDeliverOrder action.

The deliver call should contain a list of all order row ids that should be delivered. If a complete delivery of all rows should be made the list should either contain all order row ids or be empty. However if a subset of all active order rows are specified a partial delivery will be made. Partial delivery can only be made if the order has the CanDeliverOrderPartially action and each OrderRow must have action CanDeliverRow.

Response

12.3.1 Row Delivery Options

12.4 Deliver order with lower amount

Creates a delivery on a checkout order with a lower amount than the total, canceling the remaining amount. Assuming the order got CanDeliverOrder and CanCancelAmount action.

The deliver with lower amount call should be used when the delivery is complete but should not capture the full amount. All order rows will be seen as delivered.

Response

12.5 Cancel Order

Cancel an order before it has been delivered. Assuming the order has the action CanCancelOrder.

Response

If the order is successfully cancelled, Response is empty.

12.6 Cancel order amount

By specifying a higher amount than the current order cancelled amount then the order cancelled amount will increase, assuming the order has the action CanCancelOrderAmount. The delta between the new CancelledAmount and the former CancelledAmount will be cancelled.

The new CancelledAmount cannot be equal to or lower than the current CancelledAmount or more than OrderAmount on the order.

Response

If order amount is successfully cancelled, Response is empty.

12.7 Cancel order row

Changes the status of an order row to Cancelled, assuming the order has the action CanCancelOrderRow and the OrderRow has the action CanCancelRow.

Response

If order row is successfully cancelled, Response is empty.

12.8 Credit order rows

Creates a new credit on the specified delivery with specified order rows. Assuming the delivery has action CanCreditOrderRows and the specified order rows also has action CanCreditRow

Response

On the returned URL can be checked status of the task.

12.8.1 Row Crediting Options

12.9 Credit new order row

By specifying a new credit row, a new credit row will be created on the delivery, assuming the delivery has action CanCreditNewRow.

Response

On the returned URL can be checked status of the task.

12.10 Credit order rows with fee

Creates a new credit on the specified delivery with specified order rows. Assuming the delivery has action CanCreditOrderRows and the specified order rows also has action CanCreditRow. Adds the ability to add a fee to the credit.

Response

On the returned URL can be checked status of the task.

12.11 Credit amount

By specifying a credited amount larger than the current credited amount. A credit is being made on the specified delivery. The credited amount cannot be lower than the current credited amount or larger than the delivered amount.

This method requires CanCreditAmount on the delivery.

Response

If order amount is successfully credited, Response is empty.

12.12 Add order row

This method is used to add order rows to an order, assuming the order has the action CanAddOrderRow. If the new order amount will exceed the current order amount, a credit check will be performed.

Response

On the returned URL (HeaderLocation) can be checked status of the task.

12.13 Update order row

This method is used to update an order row, assuming the order has action "CanUpdateOrderRow" and the order row has the action CanUpdateRow. The method will update all fields set in the payload, if a field is not set the row will keep the current value. If the new order amount will exceed the current order amount, a credit check will be performed.

Response

If order row is successfully updated, Response is empty.

12.14 Replace order rows

This method is used to update an order row, assuming the order has action "CanUpdateOrderRow". This method will delete all the present rows and replace with the ones set in the payload. If the new order amount will exceed the current order amount, a credit check will be performed.

Response

If order row is successfully updated, Response is empty.

12.15 Data objects

12.15.1 Order

12.15.2 Delivery

12.15.3 Credit

12.15.4 Task

12.15.5 Order Row

12.15.6 Address

12.15.7 Order Status

12.15.8 Order actions

12.15.9 Delivery actions

12.15.10 Order Row actions

13. Javascript API

(Please note that the API is still considered a work in progress and might see significant changes.)

API entry point

window.scoApi is the root object for the API and contains all the operations available.

Listening for API readiness

The checkout raises an event when ready, which can be used to safely access the API.

Example:

Available operations

observeEvent(propertyString, handlerFunction) => function

Observes the client data for changes, calling the supplied function when a change is detected.

Returns a function that can be called to stop observing the specified property.

The following properties are currently supported:

Example:

setCheckoutEnabled(value) => void

Pass a false-ish value to disable the checkout. While disabled, the merchant can safely perform updates to the cart. When finished, call setCheckoutEnabled(true) to re-enable the checkout and make it reflect the changes made.