Ekspres Bank

Document Logs
Change log:

Terms and definitions:

---- 

1 - Purpose of Document

This document provides the overall technical details and design of implementing and using the functionality as specified in section 2 - Introduction. This document will not cover implementation details – for this the code base should be inspected.

2 - Introduction to Functionality

Ekspres bank is a company that can help financing a purchase by supplying a 'loan' during the purchase phase.

This means that the customer buys a phone during sign up. The customer chooses to buy through Ekspres bank who then pays for the phone.

The customer now have a 'loan' at Ekspres bank that the customer will pay back outside our system.

The process is done through three steps.

1. The customer chooses to use ekspres bank, and an container for the purchase is created at EkspresBank thorugh a Soap call (ApplicationCreate)
2. The customer is the approved or rejected. To get that information Ekspres Bank is polled for a status of the purchase through Soap (ApplicationStatus)
3. If the customer is approved we then acknowledge the purchase and send a capture message to Ekspres bank through Soap (Capture). It is also possible to cancel the purchase through Soap (cancel)

The Soap interaction is implemented and can be found at

https://svn.cdrator.com/svn/dev/integration/Financial/DK/EkspresBank/trunk

Maven dependency

<groupId>com.cdrator.integration.financial</groupId>
<artifactId>rator-financial-dk-ekspresbank</artifactId>

3 - API

There are two ways to use the implementation either through actions or if you are running on an older version of core components

Action

ApplicationCreateServiceAction

Package: com.CDRator.billing.financial.ekspresbank.action.ApplicationCreateServiceAction

This action takes in three arguments

public String execute(String orderNr, Map<String, String> fieldValues, String brandId) throws Exception

orderNr: An ordeNumber to be used in the future to identify this transaction

fieldValues: This is used to specify additional key value pairs to be used in the call to Ekspres bank. Those additional values could be channelId, duration, PrimaryAmount etc. The map contains key/values pairs channelid=1, ....

brandId: The URL for the webservice at Ekspres bank and some additional required arguments that are needed are specified in the parameter tree. This brand Id is used on a branded environment.

The action returns a string See section 4 for return values

If anything unexpected happens an exception is thrown.

ApplicationStatusServiceAction

Package: com.CDRator.billing.financial.ekspresbank.action.ApplicationStatusServiceAction

The action takes two arguments

 public String execute(String orderNr, String brandId) throws Exception

orderNr: An ordeNumber used to identify the transaction

brandId: The URL for the webservice at Ekspres bank and some additional required arguments that are needed are specified in the parameter tree. This brand Id is used on a branded environment.

The action return a string which is the 'decision' on the response from Ekspres bank.This decision is mapped from a single char to a readable response.

ACCEPT, DECLINE, REFER, CANCEL, GOAHEAD, CAPTURED, ERROR

If anything unexpected happens an exception is thrown.

CancelAction

CaptureAction

Return codes

Error Code Description
OK Everything is ok, no errors.
ERROR_LOGIN_ERROR Something is wrong with the RetailerId/Password combination.
ERROR_APPLICATION_NOTFOUND Application identified by RetailerId/OrderNr not found.
ERROR_UNKNOWN_ERROR Unexpected error occurred.
ERROR_APPLICATION_ALREADY_SUBMITTED There already is a submitted application with the given OrderNr.
ERROR_MANDATORY_FIELDS_MISSING Not all mandatory fields were provided for the requested operation.
ERROR_SITE_DISABLED The site is disabled.
ERROR_INVALID_PREFILLABLE_FIELDS There are either non-prefillable fields available or the value of some
prefillable fields are invalid.
ERROR_INVALID_HASH The hash of the fields is invalid.

Component

Brightpoint havnse response = facade.placeOrder(data);

Action API

The action API is to be used from a workflow.

PlaceOrder Action

Used for placing an order at Brightpoint@Action
@Description("Place a generic order to BrightPoint")
public class PlaceOrder {

@ActionMethod
@ReturnValue(description = @Description("String: DONE, VALIDATION_ERROR, CONNECTION_ERROR"))
public String execute(GenericOrder order) throws Exception {}
The input is a generic order which must have

GenericOrder:

• It needs a valid Account, used to find brand
• A valid deliveryAddress, COMPANY, FIRSTNAME, LASTNAME, STREET, STREETNUMBER, FLOOR, FLOOTUNIT, ZIP, CITY, PHONE
• STOCK_CODE in the parameter map on the order to set the deliverycategory
• 1-* order lines. Each of these lines must have a valid productNumber, description, orderlinenumber, TotalExclVat, and a parameter called QUANTITY, if quantity not set a default of 1 will be used

4 - Return codes

4 - Logging

The Logistic implementation will save the XML sent to and from Brightpoint to the table called SOAP_CLIENT_LOG.

6 - Configuration

Needed for polling for status of an order

ENGINE.LOGISTICS.BRIGHT_POINT.USERNAME = username

ENGINE.LOGISTICS.BRIGHT_POINT.PASSWORD = password

ENGINE.LOGISTICS.BRIGHT_POINT.ORDER_CHECK_URL = order check end point

Needed for placing an order

ENGINE.LOGISTICS.BRIGHT_POINT.USERNAME = username

ENGINE.LOGISTICS.BRIGHT_POINT.PASSWORD = password

ENGINE.LOGISTICS.BRIGHT_POINT.ORDER_URL = place order end point

ENGINE.LOGISTICS.BRIGHT_POINT.MESSAGE_TYPE = message type (example WEBSERVICE)
ENGINE.LOGISTICS.BRIGHT_POINT.DECIMAL_DELIMETER = decimal delimeter , or .
ENGINE.LOGISTICS.BRIGHT_POINT.CURRENCY_CODE = SEK, DKK, NOK
ENGINE.LOGISTICS.BRIGHT_POINT.ALLOW_BACK_ORDER = (FALSE = Hold shipment until complete; TRUE =Send the order when any product is in stock)
ENGINE.LOGISTICS.BRIGHT_POINT.SITE =site in the body (example SE100)
ENGINE.LOGISTICS.BRIGHT_POINT.ORDER_TYPE =order type, now always set to WWW
ENGINE.LOGISTICS.BRIGHT_POINT.COUNTRY_CODE =country code in the header,default is DK
ENGINE.LOGISTICS.BRIGHT_POINT.SEND_SMS_NOTIFICATION =Enables/Disables sms notification regarding shop order
ENGINE.LOGISTICS.BRIGHT_POINT.INSTANCE = Instance in the header (example SEPROD)

6 - Version