New Sale (Direct Debit)

Type:    Form
Description: Provides access to sale creation options.
Items:

Save
Saves all changes on the form.
Close
Closes the form without saving any changes.

Detail

Includes general information about new sale within the system.
¦_
Merchant Account
Code of Merchant Account to which instance of this object is attributed to.
Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.

References: Transaction.Merchant Account Code
¦_
Holder Name
Name of a payment card or bank account holder. The value is a concatenation of the firstName and lastName field values separated by a space.

Full name of the holder of the account from which merchant fees are deducted.

References: MerchantChargeInfo.holderName
¦_
Bank Account#
When Tokenization is not available and encryption is allowed on the server, the field contains encrypted credit card number or bank account number.
When Tokenization is not properly configured and encryption is not allowed on the server, transactions with sensitive data will fail and will not be processed and persisted.

References: Charge Transaction.Account Number
¦_
Token
Token that replaces account number for security purposes.

When Tokenization is enabled, each account number is replaced with a token value for persistence. Token code is automatically replaced with a real account number right before the data is sent to a Provider.

The token is stored in its internal representation (value returned by an encryption appliance). When token is returned to a client/submitter, account type and last four digits are added to it.

References: Charge Transaction.Token Code
¦_
Routing #
When transaction is associated with a credit card, the field contains card's expiration date.
When transaction is associated with a bank account, the field contains account's routing number.

References: Charge Transaction.Account Accessory
¦_
Savings
Represents the type of the account (e.g. credit card or bank account) associated with the transaction.

References: Charge Transaction.Account CL
¦_
Transaction Type
Type of transaction to be submitted.
¦_
Sale
Indicates that sale transaction is going to be submitted.
¦_
Auth
Indicates that sale-auth transaction is going to be submitted.
Amount
Total amount of the transaction.

When partial authorizations are done, amount represents required amount, which may or may not be available.

References: Transaction.Amount
Tax Amount

Amount of tax charged as part of this transaction. The value is included in the total transaction Amount.

References: Charge Transaction.Tax Amount
Fee Amount
Processing fee amount that should be charged to Merchant for processing of this transaction. Process fee amount is included in the total transaction Amount.

References: Charge Transaction.Fee Amount
Subscription Code
Code of the subscription transaction.

References: Charge Transaction.Subscription Code

References

Includes values from the transaction submitter's system.
¦_
Item Code
Value from the transaction submitter's system.

It is used to assign submitter's specific merchandise code (SKEW#, Bar Code, etc) to the transaction, to identify in the future the reason why this transaction was processed.

Usually, the value will contain a reference to a catalog item for which the payment is collected and is, therefore, only applicable in cases when a payment is collected for a single item.

References: Charge Transaction.Item Code
¦_
Transaction Code
Value from the transaction submitter's system.

It is used to assign submitter's specific transaction id to the transaction, to cross reference this transaction between two systems.

Usually, the value will contain a reference to an entity representing this transaction in submitter's front-end system.

References: Charge Transaction.Transaction Code
¦_
Customer Code
Value from the transaction submitter's system.

It is used to assign submitter's specific customer (owner) code to the transaction, to identify in the future the ownership of the transaction and to be able to cross reference the value between two systems.

Usually, the value will contain a reference to an record representing an owner of the transaction in the submitter's front-end system.

References: Charge Transaction.Customer Account Code

Billing Address

Includes information about billing address.
¦_
Street
Street of the billing address.

Both Street 1 line and Street 2 line are combined in this field.

References: Charge Transaction.Street
¦_
City
City of the billing address.

References: Charge Transaction.City
¦_
Country
Country of the billing address.
¦_
State
State of the billing address.

References: Charge Transaction.State
¦_
ZIP Code
ZIP/Postal code of the billing address.

References: Charge Transaction.ZIP Code
¦_
Phone
Billing phone or contact phone of the account holder.

References: Charge Transaction.Phone
¦_
Email
Contact email of the account holder.

References: Charge Transaction.Email

Shipping

Includes information about shipping address.
¦_
Same as Billing
Copies all the address information from billing form.
¦_
Name
First name of the person in the shipping address associated with the order/transaction

References: Charge Transaction.Shipping First Name
¦_
Street
Street of the shipping address associated with the order/transaction

References: Charge Transaction.Shipping Street
¦_
City
City of the shipping address associated with the order/transaction

References: Charge Transaction.Shipping City
¦_
Country
Country of the shipping address.
¦_
State
State of the shipping address associated with the order/transaction

References: Charge Transaction.Shipping State
¦_
ZIP Code
ZIP code of the shipping address associated with the order/transaction.

References: Charge Transaction.Shipping ZIP Code

Memo

Includes description of the transaction, might be coming from the submitter's system or assigned internally.

Descriptor

Includes information assosiated with underlying merchant (Merchant Name and Item Description fields).
¦_
Prefix
Value, used when transaction is processed through PSP or an aggregator.
¦_
Merchant Name
Name of the merchant.
¦_
Item Description
Any additional information about the item.