E-payment. Technical service description



Similar documents
E-payment. Service description

OMA SAVINGS BANK S ONLINE PAYMENT SERVICE

F o r e i g n p a y m e n t i n P o l a n d Page 1 of 6 B u s i n e s s O n l i n e

I. Payment request by WEB merchant II. Payment request by WEB merchant (direct credit card payment) III. Payment request - "Free transfer"

GTPayment Merchant Integration Manual

Shopping Cart Interface Version 1.03

Integration Guide. Rabo OmniKassa

POP BANK S ONLINE PAYMENT SERVICE

DeltaPAY v2 Merchant Integration Specifications (HTML - v1.9)

Integrate your website with Worldpay in 5 steps

Buckaroo Payment Engine 3.0 Implementation Manual HTML gateway

AS DNB banka. DNB Link specification (B2B functional description)

API Integration Payment21 Button

Payment Page Integration

Paytrail Oyj! Channel interface API! Channel model! Channel model description! Interface description!

SVEA HOSTED SERVICE SPECIFICATION V1.13

Online Banking Record Descriptions

HTML Form Widgets. Review: HTML Forms. Review: CGI Programs

MiGS Merchant Administration Guide. July 2013 Software version: MR 29

Creating International Wire Transfer Payments Reference Guide

BZWBK24 Internet. How to access the Bank? Logging on to BZWBK24 Internet: Step-by-step instruction

Integration Guide Last Revision: July 2004

Bitsquare arbitration system

MONETA.Assistant API Reference

Tutorial 6 Creating a Web Form. HTML and CSS 6 TH EDITION

How to Make Register and Make Online Bookings

Messaging API. API Specification Document Messaging API. Functionality: Send SMS Messages.

<?php if (Login::isLogged(Login::$_login_front)) { Helper::redirect(Login::$_dashboard_front); }

UPG plc Atlas Technical Integration Guide

This document is to provide help and illustrations to users who wish to deliver SMS using the Pinnacle SMS Gateway via the HTTP Protocol.

Wordware Family Website Instructions

<option> eggs </option> <option> cheese </option> </select> </p> </form>

Introduction to Client Online. Factoring Guide

Basic e-commerce. Technical integration guide for e-commerce v.3.3. Ingenico Payment Services 2014, All rights reserved.

FORM-ORIENTED DATA ENTRY

Setting up On line Account

SAP FI - Automatic Payment Program (Configuration and Run)

User Guide for Payroll Service (APS+)

PLATBA 24 Implementation Manual. Date: December 18, 2014 Version: 1.49

PayEx Merchant Administrator Manual

Hosted Credit Card Forms Implementation Guide

This Annex uses the definitions set out in the Agreement on service of payment cards on the Internet (hereinafter the Agreement).

Ariba Network Invoice Guide

The Vetuma Service of the Finnish Public Administration SAML interface specification Version: 3.5

PHP Tutorial From beginner to master

Further web design: HTML forms

MERCHANT API INTEGRATION MANUAL. Version: 2.16 <March 2016 >

PaymentNet Federal Card Solutions Cardholder FAQs

Batch Processing. Specification. Version SIX Payment Services

Basic e-commerce. Technical integration guide for e-commerce v Ogone 2013, All rights reserved.

Electronic Data Interchange (EDI)

20 CODE CHALLENGES. GCSE (9 1) Computer Science GCSE REFORM. February 2015

TERMS AND CONDITIONS OF PAYMENT ORDER IN FOREIGN EXCHANGE TRANSACTIONS AT PKO BP SA BANK

7 The Shopping Cart Module

SAP Business Intelligence ( BI ) Financial and Budget Reporting. 7.0 Edition. (Best Seller At Least 43 copies Sold)

USING MYWEBSQL FIGURE 1: FIRST AUTHENTICATION LAYER (ENTER YOUR REGULAR SIMMONS USERNAME AND PASSWORD)

QIWI Wallet Pull Payments API

Forms, CGI Objectives. HTML forms. Form example. Form example...

Paynow 3rd Party Shopping Cart or Link Integration Guide

eway AU Hosted Payment Page

Positional Numbering System

HTML Forms and CONTROLS

account multiple solutions

Process: Self Service

ESMO Online event registration instructions Register someone else or few participants (1-9 persons)

Getting Started. A Step-by-Step Guide to Trading Foreign Currencies Using the FX Solutions Global Trading System

Nordea Pankki Suomi Oyj HKO112 5/14. Nordea MasterCard. Cardholder s guide

Integration guide Rabo OmniKassa

BUSINESS 24 Banking BCR. User manual

User Documents GIFT CARD

Technical documentation

MERCHANT INTEGRATION GUIDE. Version 2.8

Creating Domestic Wire Transfer Payments Reference Guide

Easy CollECt and the transaction ManagEr interface

Q: What discounts do I get when I purchase my account in $100 increments?

SEEM4540 Open Systems for E-Commerce Lecture 06 Online Payment

Telephone Bank. Service description

Subscriptions and Recurring Payments Guide

Government of Saskatchewan Executive Council. Oracle Sourcing isupplier User Guide

SQL Injection for newbie

ipayment Gateway API (IPG API)

COMMERCIAL-IN-CONFIDENCE

CGI Programming. What is CGI?

Merchant Reporting Tool

iyzico one-off payment and installment easy payment integration

FedEx Billing Online PDF Help Guide Invoiced Customers

Using TrueCrypt to protect data

Amazon Payments Implementation Guide. Support for ZenCart

Welcome to Zoho, your online productivity and collaboration suite of

Online signature API. Terms used in this document. The API in brief. Version 0.20,

MyanPay Express Checkout Integration Guide

Alpha e-pay v2 Merchant Integration Specifications (HTML - v1.9)

User Manual. Firm Bank Manager (includes instructions for employees and firms) U.S Network of Virtual Enterprises Bank. for

Using Form Tools (admin)

Transcription:

E-payment Technical service description

p 2 (5) E-payment - Technical service description 1. Revision list ost recent change What was changed 08.08.2013 Updated seller s account to AN34 13.12.2013 Translated process description, corrected data 31.3.2016 Updatedvalue for field 4 AAB_RCV_ACCOUNT to IBAN account 2. Introduction The e-payment service, delivered by the Bank of Åland Plc through Crosskey Banking Solutions Ab Ltd, is a service that enables the buyer to buy and pay his/her purchases during an internet session. When the buyer has confirmed the payment the money is immediately transferred to the seller s account. This document describes the e-payment process, the functionality and the needed data. Lastly, a way for testing the service within the production environment is described. 3. Process description Seller 1. 8. Buyer 7. 3. 5. 4. 6. 2. Bank 1. The buyer visits the seller s web shop and chooses what products and/or services to purchase. The buyer also chooses to make the payment thru the bank s e-payment service. 2. The seller creates a foundation for payment and transfers the buyer to the bank s e-payment service. 3. The bank s e-payment service controls that the transferred seller information meets the requirements laid out in this service description. It also checks that the data is not manipulated. 4. The buyer identifies him/herself in the e-payment service with the bank s internet bank codes. 5. The service displays the payment information for the customer. 6. The buyer confirms the payment with a one use only code or terminates the payment. 7. After confirmed payment the bank examines the payment and the buyer is automatically sent back to the seller s web shop. 8. The web shop displays a webpage where it is shown that the payment is confirmed.

p 3 (5) 4. Required information and form description 4.1 Form description The form that is sent to the bank must be coded in html. The design must be as shown below. <form action= https://.../service/paybutton method=post> </form> <input name=... type=... value=... > <input name=... type=... value=... >... The Bank of Åland payment button can be copied from https://online.alandsbanken.fi//images/betalknapp/betalknapp.gif 4.2 andatory and optional information Field Information Information name Value Form /O 1 Payment version AAB_VERSION 0002 AN 4 2 Payment code AAB_STAP Code which identifies the payment AN 15 3 Invoicer ID AAB_RCV_ID AN 15 4 Seller s account AAB_RCV_ACCOUNT IBAN account AN 34 5 Seller s name AAB_RCV_NAE AN 30 6 Payment language AAB_LANGUAGE 1 = Finnish 2 = Swedish 7 Amount AAB_AOUNT Ex. 123,45 AN 19 8 Reference AAB_REF According to standard AN 20 9 Due day AAB_DATE EXPRESS = Immediate payment. N 1 AN 10 10 essage AAB_SG essage on transaction AN 245 O 11 Return-link AAB_RETURN 12 Cancel-link AAB_CANCEL 13 Reject-link AAB_REJECT URL Return link after payment URL Return link after cancellation URL Return link after rejected transaction 14 Control code AAB_AC Security code (AC-Kod) AN 32-64 15 Confirmation AAB_CONFIR YES AN 3 16 Key version AAB_KEYVERS Ex. 0001 N 4 17 Currency code AAB_CUR EUR AN 3 18 Algorithm AAB_ALG 01=D5 03=SHA256 N

p 4 (5) 4.3 Field description AN = Alphanumeric data N = Numeric data Field 1 Field 2 Field 3 Field 4 Field 5 Field 6 Field 7 Field 8 Field 9 Field 10 Field 11 Field 12 Field 13 Field 14 = andatory O = Optional E-payment version number. Code given by seller. Code can be a reference, a customer number, or a combination of ex. date, time, reference etc. Invoicer s ID, a customer code given from the bank and found on the agreement Seller s account Seller s name Language code for the service. States which language the seller uses in the web shop. The e-payment service opens in this language. The e-payment amount. As decimal separator a comma (,) is used. Please note that a dot (.) is not allowed. Reference must be a numeric value without the groups and spaces from the reference standards Due day for the payment. ust be Express if the desire is for the transaction to take place immediately. The payment message must be given in the same way as on the account extract (max. 7 rows at 35 characters). The message is only transferred to the buyer. The address to where the buyer will continue after the payment. ust be a complete URL address in HTL language with a query string or parameter information. Ex.: VALUE= http://tuote.kauppa.fi/tilaus/vahvistus.htm The address to where the buyer will continue after cancelation of payment. Ex.: VALUE= http://tuote.kauppa.fi/tilaus/keskeytys.htm The address to where the buyer will continue if a technical error occurs in the e-payment service. Ex.: VALUE= http://tuote.kauppa.fi/tilaus/virhe.htm The payment s control code, calculated with help of the algorithm chosen in field 18 in the following way: 1. A character string is created based on the fields: AAB_VERSION& AAB_STAP& AAB_RCV_ID& AAB_AOUNT& AAB_REF& AAB_DATE& AAB_CUR& Seller security code& Note! When SHA256 is used the security code needs to be converted from hexadecimal to string before it is used in the calculation. The character string does not have spaces and the & character is included in the calculation. The e-payment version is 0002 and the information must be in the same order as above. 2. Based on the character string above a hash value is calculated with the chosen algorithm. The value is then translated into hexadecimal form. The received hash value is put in Field 14 Control code. With help of the control code the receiver of the message controls the sender and that the message is not manipulated. Seller security code is given when the service is connected and agreed upon.

p 5 (5) Field 15 Field 16 Field 17 Field 18 Seller receives information regarding the handling of the payment in the return link. Version number of the security code used in the calculation of the AC code. Transaction currency must be EUR. Chosen algorithm, 01=D5, 03=SHA-256 5. Return information Field Information Information name 1 Payment version AAB-RETURN-VERSION 2 Payment code AAB-RETURN-STAP 3 Payment reference AAB-RETURN-REF 4 The bank s archive code AAB-RETURN-PAID 5 Calculated control code AAB-RETURN-AC 5.1 andatory and optional information Field 1 Field 2 Field 3 Field 4 Field 5 Returns the e-payment version number Returns the information/code given by the seller in the field AAB_STAP. The code can be a reference, a customer number, or a combination of ex. date, time, reference etc. Returns the reference given by the seller when creating the e-payment The archive code created by the bank The return control code is calculated the same way as the payment control code. It uses the chosen algorithm and the following information: AAB-RETURN-VERSION& AAB-RETURN-STAP& AAB-RETURN-REF& AAB-RETURN-PAID& Seller security code& The character string does not have spaces and the & character is included in the calculation. Example of return link with control code: Original return link: VALUE= http://tuote.kauppa.fi/tilaus/vahvistus.htm Contents in return-url: http://tuote.kauppa.fi/tilaus/vahvistus.htm?aab-return-ver- SION=0002&AAB-RETURN-STAP=1234567890&AAB-RETURN- REF=123&AAB-RETURN-PAID=20020912600290018867&AA B-RETURN-AC=69E6574CDC3498F32C43E0DD39C3B21A

p 6 (5) 6. Testing Test customers To make it possible to test the e-payment service in the production environment there is a test seller and a test customer implemented in the system. Please note that it is only possible to test with these two test customers, in other words it is not possible to use a real customer against test seller or test customer against real seller. The test customer has a static username, password and PIN-code, as indicated below. Production link: https://online.alandsbanken.fi/service/paybutton Test customers: PIN: any number containing 4 figures Seller AAB_RCV_ID : AAB_AC: AAB_RCV_ACCOUNT Customer User id (Användar-ID/ Käyttäjätunnus): Password (Lösenord/ Salasana): PIN (Ange kod/ Anna tunnusluku): AABESHOPID PAPEGOJA FI77 6601 0001 1308 55 12345678 123456 Any number containing 4 figures