<< Click to Display Table of Contents >> Navigation: iVend Database Database > Tables > CfgPaymentProcessorSetup Table |
Navigation: iVend Database Database > Tables >
iVend 6.6 Database Help
CfgPaymentProcessorSetup Table
Collapse All Expand All
iVend Database Database : CfgPaymentProcessorSetup Table |
Description
We can specify the payment processor required by the merchant and can setup the assembly info and other details like card type: visa/ master etc.
Properties
Creation Date |
4/13/2015 12:00 PM |
File Group |
PRIMARY |
Text File Group |
PRIMARY |
System Object |
|
Published for Replication |
|
Rows |
0 |
Data Space Used |
0.00 KB |
Index Space Used |
0.00 KB |
Columns
|
Column Name |
Description |
Datatype |
Length |
Allow Nulls |
Default |
Formula |
PaymentProcessorSetupKey |
Value is the system generated Primary Key of the table. |
VarWChar |
50 |
|
|
|
|
|
AccountType |
Value is the card type. Valid values are: Others = 0 MasterCard = 1 Visa = 2 Amex = 3 DinersClub = 4 Discover = 5 JCB = 6 CartBlance = 7 |
Integer |
4 |
|
|
|
|
Id |
Value is the Id of the payment processor. E.g. OGONE, DPS (Card Authorizing gateway). |
VarWChar |
20 |
|
|
|
|
Description |
Value is the description of the payment processor. |
VarWChar |
100 |
|
|
|
|
AssemblyName |
Value is the assembly information i.e. the complete path where the assembly for the processor is kept. |
VarWChar |
200 |
|
|
|
|
ClassName |
Value is the class name which handles the processor in assembly. |
VarWChar |
200 |
|
|
|
|
Location |
Value is the path where the hardware assemblies can be found. |
VarWChar |
200 |
|
|
|
|
Created |
Date of creation of this record |
DBTimeStamp |
4 |
|
|
|
|
CreatedBy |
Reference of user who has created this record. See also Security User |
VarWChar |
50 |
|
|
|
|
Modified |
Date of last modification of this record |
DBTimeStamp |
4 |
|
|
|
|
ModifiedBy |
Reference of user who has modified this record. See also Security User |
VarWChar |
50 |
|
|
|
|
StoreKey |
Reference Key for the Store |
VarWChar |
50 |
|
|
|
|
IsMobileProcessor |
Value is True if the Payment Processor is setup at mobile |
Boolean |
1 |
|
((0)) |
|
|
ParentConfigData |
Store the device specific configuration information in XML format. E.g. Login Id, Password etc |
Xml |
16 |
|
|
Indexes
Index |
Description |
Primary |
Unique |
|
SQL
SET ANSI_NULLS ON SET QUOTED_IDENTIFIER ON CREATE TABLE [dbo].[CfgPaymentProcessorSetup]( [PaymentProcessorSetupKey] [nvarchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, [AccountType] [int] NOT NULL, [Id] [nvarchar](20) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, [Description] [nvarchar](100) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [AssemblyName] [nvarchar](200) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, [ClassName] [nvarchar](200) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, [Location] [nvarchar](200) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, [Created] [datetime] NOT NULL, [CreatedBy] [nvarchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, [Modified] [datetime] NOT NULL, [ModifiedBy] [nvarchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL, [StoreKey] [nvarchar](50) COLLATE SQL_Latin1_General_CP1_CI_AS NULL, [IsMobileProcessor] [bit] NOT NULL, [ParentConfigData] [xml] NULL, CONSTRAINT [PK_CfgPaymentProcessorSetup] PRIMARY KEY CLUSTERED ( [PaymentProcessorSetupKey] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY] ALTER TABLE [dbo].[CfgPaymentProcessorSetup] ADD CONSTRAINT [DF_CfgPaymentProcessorSetup_IsMobileProcessor] DEFAULT ((0)) FOR [IsMobileProcessor] |
See Also
© 2019 All Rights Reserved.
Send comments on this topic.