Contents
- File Modified No files shared here yet.
- 1 - Purpose of Document
- 2 - Introduction to Functionality
- 3 - Architecture and Design
- 3.1 - Object Model
- 3.2 - Data Model
- 3.2.1 - SEPA_PAYMENT Table
- Unknown macro: {table-plus} Name Type Description ID NUMBER STATUS_ID NUMBER Status used by the engine to process the records. FILE_NAME VARCHAR (200CHAR) The XML file name. DESCRIPTION VARCHAR (200CHAR) Field used to write information. TYPE NUMBER Indicates the type of payment (Direct Debit / Credit Transfer) . CREATION_DATE DATE Creation date of the file TRANSACTION_NUMBER NUMBER Number of transactions. TOTAL_SUM NUMBER Total amount of all transactions. INITIAL_PARTY_NAME VARCHAR(70CHAR) The party that initiates the transaction. Max 70 characters. Unknown macro: {table-plus} 3.2.3 - SEPA_PAYMENT_INFO Table "> Unknown macro: {table-plus} Name Type Description ID NUMBER STATUS_ID NUMBER Status used by the engine to process the records. FILE_NAME VARCHAR (200CHAR) The XML file name. DESCRIPTION VARCHAR (200CHAR) Field used to write information. TYPE NUMBER Indicates the type of payment (Direct Debit / Credit Transfer) . CREATION_DATE DATE Creation date of the file TRANSACTION_NUMBER NUMBER Number of transactions. TOTAL_SUM NUMBER Total amount of all transactions. INITIAL_PARTY_NAME VARCHAR(70CHAR) The party that initiates the transaction. Max 70 characters. Unknown macro: {table-plus}
- 3.2.3 - SEPA_PAYMENT_INFO Table
Document Logs
Change log:
Date: |
Author: |
Version: |
Changes: |
Completed |
Ext. |
Int. |
Is in Core |
---|---|---|---|---|---|---|---|
Unknown macro: {page-info} |
Unknown macro: {page-info} |
0.1 |
Doc. created |
Yes/No |
|
|
|
Terms and definitions:
Terms/definitions: |
Meaning: |
---|---|
TBD |
To be defined |
N/A |
Not applicable |
1 - Purpose of Document
The purpose of this document is to provide an overview of the functionality and implementation of the SEPA Payment Engines.
2 - Introduction to Functionality
SEPA stands for Single Euro Payment Area. The objective of the SEPA is to provide standars for euro payments. All payments under this regulation are treated as domestic transactions. SEPA allows users to make payment transactions in Euro from a single bank account within Europe. SEPA offers a set of instruments to treat these payment transactions (SEPA Credit Transfers and SEPA Direct Debits)in an easy and secure way.
3 - Architecture and Design
All the payment transactios are XML based. In order to support the XML file generation and XML processing (reading) two Engines will be implemented:
- SEPA Generator: This engine will read the information from the SEPA Payment table and create the SEPA XML file depending on the payment type (Direct Debit or Credit Transfer).
- SEPA Reader: This engine will read the incoming SEPA XML and updte the corresponding SEPA tables.
3.1 - Object Model
The following diagram presents the main classes of the SEPA Generator:
3.2 - Data Model
The SEPA Engines use specific tables to retrieve and store information. The following ER diagram shows the relationship between the tables of the SEPA Generator Engine:
Table Name |
Description |
---|---|
SEPA_PAYMENT |
This is the table used by the SEPA Generator Engine to create the SEPA XML files. Contains information for the XML header section like Create date, number of transactions, etc. |
SEPA_PAYMENT_INFO |
Contains information related to the payment: Creditor Info / Debitor Info depending on the type of transaction. |
SEPA_PAYMENT_TRANS_INFO |
Contains information specific to the individual transactions. |
3.2.1 - SEPA_PAYMENT Table
Unknown macro: {table-plus}
Name |
Type |
Description |
||
---|---|---|---|---|
ID |
NUMBER |
|
||
STATUS_ID |
NUMBER |
Status used by the engine to process the records. |
||
FILE_NAME |
|
VARCHAR (200CHAR) |
|
The XML file name. |
DESCRIPTION |
|
VARCHAR (200CHAR) |
|
Field used to write information. |
TYPE |
|
NUMBER |
|
Indicates the type of payment (Direct Debit / Credit Transfer) . |
CREATION_DATE |
DATE |
Creation date of the file |
||
TRANSACTION_NUMBER |
NUMBER |
Number of transactions. |
||
TOTAL_SUM |
NUMBER |
Total amount of all transactions. |
||
INITIAL_PARTY_NAME |
|
VARCHAR(70CHAR) |
|
The party that initiates the transaction. Max 70 characters. |
Name |
Type |
Description |
||
---|---|---|---|---|
ID |
NUMBER |
|
||
STATUS_ID |
NUMBER |
Status used by the engine to process the records. |
||
FILE_NAME |
|
VARCHAR (200CHAR) |
|
The XML file name. |
DESCRIPTION |
|
VARCHAR (200CHAR) |
|
Field used to write information. |
TYPE |
|
NUMBER |
|
Indicates the type of payment (Direct Debit / Credit Transfer) . |
CREATION_DATE |
DATE |
Creation date of the file |
||
TRANSACTION_NUMBER |
NUMBER |
Number of transactions. |
||
TOTAL_SUM |
NUMBER |
Total amount of all transactions. |
||
INITIAL_PARTY_NAME |
|
VARCHAR(70CHAR) |
|
The party that initiates the transaction. Max 70 characters. |