AuthKey*string
Specifies the Auth-Key, which authorizes the Host system to use the SPIn Web Service. Necessary for all SPIn Proxy connections, optional for direct terminal connections.
PaymentType*string
Identifies the EDC (Electronic Data Capture) type — Credit, Debit, EBT_Food, EBT_Cash (Electronic Benefits Transfer), userChoice, or Gift.
- If
userChoice is sent, the terminal lets the customer choose between Credit, Debit, or EBT during payment; the response's PaymentType field reflects the option the customer actually selected. See the TransType field for which transaction types each PaymentType supports.
Lengthlength <= 20
Value in"Credit" | "Debit" | "EBT_Food" | "EBT_Cash" | "userChoice" | "Gift"
TransType*string
Identifies the type of transaction to run. Balance applies only to EBT_Food/EBT_Cash.
Supported TransType values per PaymentType (US):
- Credit: Sale, Return, Void, Auth, Capture, CashAdvance*
- Debit: Sale, Return
- EBT_Food: Sale, Return
- EBT_Cash: Sale, Return
- Gift: Activate, Inquire, Redeem, Refund, Reload, Deactivate, Reissue, Void
* CashAdvance is only available for certain processors.
Amount*number
Dollar amount of the transaction ($$$$$$$.CC) — the total amount, including tip if one was added (base + tip). Not used for Loyalty transactions, which use a Points value instead. Must always be a positive value, even for Returns.
Tip?number
Specifies the tip amount in dollars to be applied to the transaction. Tip must be enabled on the payment terminal..
CashbackAmount?number
Cashback amount of the transaction ($$$$$$$.CC). Only valid on Debit or EBT payment types. Available on builds later than 5/17/19 and Aura.
Frequency?string
Indicates whether this is a one-time or recurring transaction.
CustomFee?number
Dollar amount of the transaction ($$$$$$$.CC). Whatever fee type is enabled in the TPN configuration, the provided amount will be considered the custom fee.
IsvId?string
16-character alphanumeric ISV identifier, e.g. 100001 for CP-PINPAD (cloud POS pinpad transaction).
ReconId?string
Used for reconciliation purposes. Applicable only to Fiserv North and Elavon transactions, and optional. An alphanumeric reference ID linking the transaction to its corresponding settlement record — 11 characters for Fiserv North, 24 characters for Elavon.
RefId*string
Alphanumeric reference field that must be unique within the scope of an open batch. Set by the host system and mandatory for all deployments. Used for Tip or other transaction-adjustment requests related to a specific transaction (e.g. Tip Adjustment or Void Transaction). For the Table payment type, the RefId does not need to be unique within a batch.
RegisterId*string
Alphanumeric reference field.
TPN?string
Alphanumeric. Can be used instead of RegisterId, only for Dejavoo SPIn Proxy connections — e.g. <RegisterId>21123001</RegisterId><AuthKey>12345678</AuthKey> works the same as <TPN>12345678912</TPN><AuthKey>12345678</AuthKey>.
PrintReceipt?string
No = transaction receipt won't be printed on the terminal; Merchant = print Merchant copy only; Customer = print Customer copy only; Both = print both Merchant and Customer copies (default).
Lengthlength <= 50
Value in"No" | "Merchant" | "Customer" | "Both"
ReducedStateTax?string
Reduced state tax applied to this transaction. Reduced tax must be enabled on the terminal.
StateTax?string
State tax applied to this transaction. Tax must be enabled on the terminal.
CityTax?string
City tax applied to this transaction. Tax must be enabled on the terminal.
SigCapture?string
If set to "No", the terminal suppresses the signature capture event during the transaction. If not included or set to "Yes", the terminal captures a signature (if the terminal supports signature capture).
Lengthlength <= 3
Value in"Yes" | "No"
Tag1?string
The portal supports up to three tags. Tag labels can be enabled for the TPN from the portal via S.T.E.A.M → Search and Select TPN → Edit Parameter → Value Add → Enable Tag the Tx. The label for each tag must be configured in Edit Parameter. Once processed, the tag value is printed on the merchant copy of the receipt; transactions can also be filtered by this tag value on the portal, and the settlement report includes it.
PerformedBy?string
Identifies the user who performed the transaction. For a Cloud POS + PIN pad transaction, this identifies the merchant user (i.e. the merchant's email ID) who initiated it. The terminal uploads this information to the portal as part of the signature upload process; it's visible on the portal and included in the downloadable transaction report.
MerchantId?string
Optional for regular transactions when Multi MID (MMID) is not enabled. Mandatory when MMID is enabled — must be the TPN through which the transaction is intended to be processed. In the iPOSpays environment, each MID is tied to a specific TPN, so the correct TPN must be sent to route the transaction to the appropriate MID, e.g. <AuthKey>12345678</AuthKey><TPN>MasterTPN</TPN><MerchantId>TransactingTPN</MerchantId>.
CustomerEmail?string
Used to send the customer's email address.
CustomerMobile?string
Used to send the customer's mobile number. If provided, the country code (extension) is mandatory (e.g. +1) along with a valid 10-digit phone number.
IsTxnStatusScreenRequired?boolean
Indicates whether the terminal should display the transaction status screen after processing.