Managed Rebill web services
|
|
|
- Noel Pope
- 8 years ago
- Views:
Transcription
1 Web Active Corporation Managed Rebill web services Data type and field specifications Moe Oo 10/02/2009 Version 1.5
2 Contents Introduction... 4 Data Field Specifications... 5 Return format for Query Next Transaction... 7 Request format for Query Transactions... 8 Return format for Query Transactions... 8 Validation on Customer Create Rebill Customer Update Rebill Customer Query Rebill Customer Delete Rebill Customer Validation on Rebill Event Validataion on Transaction Query Next Transaction Query Transactions Appendix A: Request and Response Format for Customer Create Rebill Customer Update rebill Customer Query Rebill Customer Delete Rebill Customer Appendix B: Request and Response Format for Event Create Rebill Event Update Rebill Event Query Rebill Event Delete Rebill Event Appendix C: Request and Response format for Transactions... 28
3 Query Next Transaction Query Transactions Appendix D: Test procedures... 31
4 Introduction This document will specify the methods which are available in managed rebill web service. It also explains the request and response format of the web services; field specification and validation required in managing rebill payments. The following methods are available. Create Rebill Customer Create Rebill Event Delete Rebill Customer Delete Rebill Event Query Rebill Customer Query Rebill Event Update Rebill Customer Update RebillEvent Query Next Transaction Query Transactions To able to call the above web service methods, ewaycustomerid, username and password need to specify in soap header.
5 Data Field Specifications The following table lists all the field names and their maximum length, and it also specifies the required fields. Soap Header Maximum Field length Required ewaycustomerid 8 Username 100 Password 50 Request Fields CustomerRef 20 CustomerTitle 20 CustomerFirstName 50 CustomerLastName 50 CustomerCompany 100 CustomerJobDesc 50 Customer 50 CustomerAddress 255 CustomerSuburb 50 CustomerState 50 CustomerPostCode 6
6 CustomerCountry 50 CustomerPhone1 20 CustomerPhone2 20 CustomerFax 20 CustomerURL 255 CustomerComments 255 RebillInvRef 255 RebillInvDesc 255 RebillCCName 50 RebillCCNumber 19 RebillCCExpMonth 2 RebillCCExpYear 4 RebillInitAmt 10 RebillInitDate 10 RebillRecurAmt 10 RebillStartDate 10 RebillInterval 2 RebillIntervalType 1 RebillEndDate 10
7 Response Fields Result 10 ErrorSeverity 50 ErrorDetails 255 RebillCustomerID 8 RebillID 8 Return format for Query Next Transaction Following transaction details will be returned for querying next transaction. Field Type Note/Example TransactionDate Datetime CardHolderName String Joe Smith ExpiryDate String (mm/yy) 11/12 Amount String This will return in cent format. e.g 200 for $2.00
8 Request format for Query Transactions Field Type Note/Example RebillCustomerID Int (Required) This must be id of active customer. RebillID Int (Required) This must be id of active rebill event. StartDate Datetime (Optional) To return the transactions after specified start date. E.g EndDate Datetime (Optional) To return the transactions before specified end date. E.g Status String (Optional) To return the transactions for only specified status. The status must be either Future, Pending, Successful or Failed NOTE: If you don t specify any of optional values; start date, end date or status, the result will return every transactions belong to the specified rebill event. Return format for Query Transactions Following transaction details will be returned for querying transactions. Field Type Note/Example TransactionDate Datetime Amount String This will return in cent format. e.g 200 for $2.00 Status String Transaction status will be one of these values; Future,
9 Pending, Successful or Failed Type String Transaction type will be one of these two values; Recurring or Initial. TransactionNumber String This is a resulted transaction number. e.g This will return an empty string for future and pending transactions. TransactionError String This is a transaction result description. e.g. 10,Approved or 05,Declined This will return an empty string for future and pending transactions.
10 Validation on Customer Create Rebill Customer When creating a customer, the following validation rules apply. Customer First Name is required. Customer Last Name is required. and URL must be in valid format. Update Rebill Customer When updating customer details, the following validation rules apply. Rebill Customer ID is required and it must be an existing customer id. Customer First Name is required. Customer Last Name is required. and URL must be in valid format. Query Rebill Customer Rebill Customer ID is required and it must be an existing customer id. Delete Rebill Customer Rebill Customer ID is required and it must be an existing customer id. If current rebill customer has any active rebill events, customer cannot be deleted.
11 Validation on Rebill Event When creating or updating rebill event, the following validations apply. All fields are required except invoice reference and invoice description. RebillCustomerID is required and must be a valid customer id. RebillID is a required field in update method and it should be an existing id which belongs to above rebill customer. RebillCCNumber This field is customer s credit card and it must be a valid card. When existing card data is retrieved, the web service will return the part of credit card number which is in the format of (44443XXXXXXX1111). If you not intend to change the credit card details while you update other rebill event details, you can pass back the credit card format that you retrieved. If you want to update the credit card, new credit card number should be passed. RebillCCExpMonth - The expiry month of your customer's credit card. (Must not be an expired credit card). RebillCCExpYear - The expiry year of your customer's credit card. Format must be either (yy or yyyy) eg. 06 or (Must not be an expired credit card) RebillInitAmt - The initial payment amount of the rebill event. Enter 0 if initial payment is not required. RebillInitDate - The date of the initial payment of the rebill event. Enter today s date if no initial payment is required. Format must of dd/mm/yyyy. Initial date must be same or before RebillStartDate. If you not intend to change the initial date while you update other rebill event details, you can pass back the original initial date that you retrieved. RebillRecurAmt - The recurring payment amount of the rebill. The value must be greater than 0. RebillStartDate - The date of the first recurring payment. Format must of dd/mm/yyyy. The date must be today or greater than today date and must be greater than RebillInitDate. RebillInterval - The size of the interval between recurring payments (used in conjunction with RebillIntervalType). The value must be 1 to 31 only. RebillIntervalType - The type of Interval. (1 = Days, 2 = Weeks, 3 = Months, 4 = Years). The value must be only 1 or 2 or 3 or 4.
12 eg. If payment is every 3 weeks, enter 3 in the RebillInterval field and 2 in the RebillIntervalType field. RebillEndDate - The date that recurring payments are to stop. Format must of dd/mm/yyyy. This date must be after RebillStartDate.
13 Validataion on Transaction Query Next Transaction RebillCustomerID is required and must be a valid customer id. RebillID is a required field and it should be an existing id which belongs to above rebill customer. Query Transactions As transaction details are sensitive data, the request parameters must be 100% valid. Otherwise an exception will be thrown or no transactions data will be returned. RebillCustomerID is required and must be a valid customer id. If this id is not valid or not belonged to current eway merchant, no transactions data will be returned. RebillID is a required field and it should be an existing id which belongs to above rebill customer. If it is not a valid Id or not belonged to rebill customer, no transactions data will be returned. StartDate is an optional value but if it is passed, it must be date time value. EndDate is an optional value but if it is passed, it must be date time value. Status is an optional value but if it is passed, it must be one of the valid statuses. The valid statuses are Future, Pending, Successful and Failed.
14 Appendix A: Request and Response Format for Customer Create Rebill Customer Request <soap:header> <ewayheader xmlns=" <ewaycustomerid> </ewaycustomerid> <Password>test</Password> </ewayheader> </soap:header> <soap:body> <CreateRebillCustomer xmlns=" <customertitle>mr</customertitle> <customerfirstname>joe</customerfirstname> <customerlastname>bloggs</customerlastname> <customeraddress>bloggs Enterprise</customerAddress> <customersuburb>capital City</customerSuburb> <customerstate>act</customerstate> <customercompany>bloggs</customercompany> <customerpostcode>2111</customerpostcode> <customercountry>australia</customercountry> <customerfax> </customerfax> <customerphone1> </customerphone1> <customerphone2></customerphone2> <customerref>ref123</customerref> <customerjobdesc></customerjobdesc> <customercomments>please Ship ASASP</customerComments> <customerurl> </CreateRebillCustomer> </soap:body> Successful Response <CustomerDetails> <Result>Success</Result> <ErrorSeverity />
15 <ErrorDetails /> </CustomerDetails> Failed Response <CustomerDetails> <Result>Fail</Result> <ErrorSeverity>Error</ErrorSeverity> <ErrorDetails>The 'CustomerFirstName' element has an invalid value according to its data type.</errordetails> <RebillCustomerID>0</RebillCustomerID> </CustomerDetails>
16 Update rebill Customer Request <soap:header> <ewayheader xmlns=" <ewaycustomerid> </ewaycustomerid> <Password>test</Password> </ewayheader> </soap:header> <soap:body> <UpdateRebillCustomer xmlns=" <RebillCutomerID> </RebillCutomerID> <customertitle>mr</customertitle> <customerfirstname>joe</customerfirstname> <customerlastname>bloggs Enterprise</customerLastName> <customeraddress>capital City</customerAddress> <customersuburb>capital City</customerSuburb> <customerstate>act</customerstate> <customercompany>bloggs</customercompany> <customerpostcode>2111</customerpostcode> <customercountry>australia</customercountry> <customerfax> </customerfax> <customerphone1> </customerphone1> <customerphone2></customerphone2> <customerref>ref123</customerref> <customerjobdesc>bloggs</customerjobdesc> <customercomments>please Ship ASASP</customerComments> <customerurl> </UpdateRebillCustomer> </soap:body> Successful Response <CustomerDetails> <Result>Success</Result> <ErrorSeverity /> <ErrorDetails />
17 </CustomerDetails> Failed Response <CustomerDetails> <Result>Fail</Result> <ErrorSeverity>Error</ErrorSeverity> <ErrorDetails>The 'CustomerFirstName' element has an invalid value according to its data type.</errordetails> <RebillCustomerID>0</RebillCustomerID> </CustomerDetails>
18 Query Rebill Customer Request <soap:header> <ewayheader xmlns=" <ewaycustomerid> </ewaycustomerid> <Password>test</Password> </ewayheader> </soap:header> <soap:body> <QueryRebillCustomer xmlns=" <RebillCustomerID> </RebillCustomerID> </QueryRebillCustomer> </soap:body> Successful Response <CustomerDetails> <Result>Success</Result> <ErrorSeverity /> <ErrorDetails /> <CustomerRef>8989</CustomerRef> <CustomerTitle>Mr</CustomerTitle> <CustomerFirstName>Joe</CustomerFirstName> <CustomerLastName>Blogg</CustomerLastName> <CustomerCompany>eWAY</CustomerCompany> <CustomerJobDesc></CustomerJobDesc> <CustomerAddress>Capital City</CustomerAddress> <CustomerSuburb>Phillips</CustomerSuburb> <CustomerState>act</CustomerState> <CustomerPostCode>2607</CustomerPostCode> <CustomerCountry>Australia</CustomerCountry> <CustomerPhone1> </CustomerPhone1> <CustomerPhone2> </CustomerPhone2> <CustomerFax> </CustomerFax> <CustomerURL>eway.com</CustomerURL> <CustomerComments>test</CustomerComments> </CustomerDetails>
19 Failed Response <CustomerDetails> <Result>Fail</Result> <ErrorSeverity>Error</ErrorSeverity> <ErrorDetails>Customer does not exist.rebill customer details cannot be retrived.</errordetails> </CustomerDetails>
20 Delete Rebill Customer Request <soap:header> <ewayheader xmlns=" <ewaycustomerid> </ewaycustomerid> <Password>test</Password> </ewayheader> </soap:header> <soap:body> <DeleteRebillCustomer xmlns=" <RebillCustomerID> </RebillCustomerID > </DeleteRebillCustomer> </soap:body> Successful Response <CustomerDetails> <Result>Success</Result> <ErrorSeverity /> <ErrorDetails /> </CustomerDetails> Failed Response <CustomerDetails> <Result>Fail</Result> <ErrorSeverity>Error</ErrorSeverity> <ErrorDetails>Customer does not exist.rebill customer cannot be deleted.</errordetails> <RebillCustomerID /> </CustomerDetails>
21 Appendix B: Request and Response Format for Event Create Rebill Event Request <soap:envelope xmlns:xsi=" xmlns:xsd=" xmlns:soap=" <soap:header> <ewayheader xmlns=" <ewaycustomerid> </ewaycustomerid> <Password>test</Password> </ewayheader> </soap:header> <soap:body> <CreateRebillEvent xmlns=" <RebillInvRef>ref123</RebillInvRef> <RebillInvDes></RebillInvDes> <RebillCCName>test</RebillCCName> <RebillCCNumber> </RebillCCNumber> <RebillCCExpMonth>07</RebillCCExpMonth> <RebillCCExpYear>07</RebillCCExpYear> <RebillInitAmt>100</RebillInitAmt> <RebillInitDate>08/06/2007</RebillInitDate> <RebillRecurAmt>100</RebillRecurAmt> <RebillStartDate>05/06/2007</RebillStartDate> <RebillInterval>1</RebillInterval> <RebillIntervalType>1</RebillIntervalType> <RebillEndDate>08/07/2007</RebillEndDate> </CreateRebillEvent> </soap:body> Successful Response <RebillEventDetails> <Result>Success</Result> <ErrorSeverity /> <ErrorDetails /> <RebillID> </RebillID>
22 </RebillEventDetails> Failed Response <RebillEventDetails> <Result>Fail</Result> <ErrorSeverity>Error</ErrorSeverity> <ErrorDetails>The 'RebillRecurAmt' element has an invalid value according to its data type.</errordetails> </RebillEventDetails>
23 Update Rebill Event Request <soap:header> <ewayheader xmlns=" <ewaycustomerid> </ewaycustomerid> <Password>test</Password> </ewayheader> </soap:header> <soap:body> <UpdateRebillEvent xmlns=" <RebillID> </RebillID> <RebillInvRef>Ref123</RebillInvRef> <RebillInvDes></RebillInvDes> <RebillCCName>test</RebillCCName> <RebillCCNumber>44443XXXXXXX1111</RebillCCNumber> <RebillCCExpMonth>07</RebillCCExpMonth> <RebillCCExpYear>07</RebillCCExpYear> <RebillInitAmt>100</RebillInitAmt> <RebillInitDate>08/06/2007</RebillInitDate> <RebillRecurAmt>100</RebillRecurAmt> <RebillStartDate>05/06/2007</RebillStartDate> <RebillInterval>1</RebillInterval> <RebillIntervalType>1</RebillIntervalType> <RebillEndDate>08/07/2007</RebillEndDate> </UpdateRebillEvent> </soap:body> Successful Response <RebillEventDetails> <Result>Success</Result> <ErrorSeverity /> <ErrorDetails /> <RebillID> </RebillID> </RebillEventDetails>
24 Failed Response <RebillEventDetails> <Result>Fail</Result> <ErrorSeverity>Error</ErrorSeverity> <ErrorDetails>The 'RebillCCExpMonth' element has an invalid value according to its data type.</errordetails> <RebillID> </RebillID> </RebillEventDetails>
25 Query Rebill Event Request <soap:header> <ewayheader xmlns=" <ewaycustomerid> </ewaycustomerid> </Username> <Password>test</Password> </ewayheader> </soap:header> <soap:body> <QueryRebillEvent xmlns=" <RebillID> </RebillID> </QueryRebillEvent> </soap:body> Successful Response <RebillEventDetails> <Result>Success</Result> <ErrorSeverity /> <ErrorDetails /> <RebillID> </RebillID> <RebillInvRef>Ref123</RebillInvRef> <RebillInvDesc /> <RebillCCName>test</RebillCCName> <RebillCCNumber>44443XXXXXXX1111</RebillCCNumber> <RebillCCExpMonth>07</RebillCCExpMonth> <RebillCCExpYear>07</RebillCCExpYear> <RebillInitAmt>100</RebillInitAmt> <RebillInitDate>08/06/2007</RebillInitDate> <RebillRecurAmt>100</RebillRecurAmt> <RebillStartDate>05/06/2007</RebillStartDate> <RebillInterval>1</RebillInterval> <RebillIntervalType>1</RebillIntervalType> <RebillEndDate>08/07/2007</RebillEndDate> </RebillEventDetails>
26 Failed Response <RebillEventDetails> <Result>Fail</Result> <ErrorSeverity>Error</ErrorSeverity> <ErrorDetails>The 'RebillID' element has an invalid value according to its data type.</errordetails> <RebillID /> </RebillEventDetails>
27 Delete Rebill Event Request <soap:header> <ewayheader xmlns=" <ewaycustomerid> </ewaycustomerid> <Password>test</Password> </ewayheader> </soap:header> <soap:body> <DeleteRebillEvent xmlns=" <RebillID> </RebillID> </DeleteRebillEvent> </soap:body> Successful Response <RebillEventDetails> <Result>Success</Result> <ErrorSeverity /> <ErrorDetails /> <RebillID> </RebillID> </RebillEventDetails> Failed Response <RebillEventDetails> <Result>Fail</Result> <ErrorSeverity>Error</ErrorSeverity> <ErrorDetails>The 'RebillID' element has an invalid value according to its data type.</errordetails> <RebillID>abc</RebillID> </RebillEventDetails>
28 Appendix C: Request and Response format for Transactions Query Next Transaction Request <soap:header> <ewayheader xmlns=" <ewaycustomerid> </ewaycustomerid> <Password>test123</Password> </ewayheader> </soap:header> <soap:body> <QueryNextTransaction xmlns=" <RebillID> </RebillID> </QueryNextTransaction> </soap:body> Successful Response <soap:body> <QueryNextTransactionResponse xmlns=" <QueryNextTransactionResult> <TransactionDate> T00:00:00</TransactionDate> <CardHolderName>Test Card </CardHolderName> <ExpiryDate>12/10</ExpiryDate> <Amount>250</Amount> </QueryNextTransactionResult> </QueryNextTransactionResponse> </soap:body> Failed Response It will throw exception if there is any login error.
29 Query Transactions Request (Without optional values) <soap:header> <ewayheader xmlns=" <ewaycustomerid> </ewaycustomerid> <Password>test123</Password> </ewayheader> </soap:header> <soap:body> <QueryTransactions xmlns=" <RebillID> </RebillID> </QueryTransactions> </soap:body> Request (With optional values) <soap:header> <ewayheader xmlns=" <ewaycustomerid> </ewaycustomerid> <Password>test123</Password> </ewayheader> </soap:header> <soap:body> <QueryTransactions xmlns=" <RebillID> </RebillID> <startdate> </startdate> <enddate> </enddate> <status>future </status> </QueryTransactions> </soap:body>
30 Successful Response <soap:body> <QueryTransactionsResponse xmlns=" <QueryTransactionsResult> <rebilltransaction> <TransactionDate> T00:00:00+11:00</TransactionDate> <Amount>33600</Amount> <Status>Successful</Status> <Type>Initial</Type> <TransactionNumber> </TransactionNumber> <TransactionError>10,Approved</TransactionError> </rebilltransaction> <rebilltransaction> <TransactionDate> T00:00:00+11:00</TransactionDate> <Amount>33600</Amount> <Status>Failed</Status> <Type>Recurring</Type> <TransactionNumber>0</TransactionNumber> <TransactionError>eWAY Error: Invalid Expiry Date. Your credit card has not been billed for this transaction.</transactionerror> </rebilltransaction> </QueryTransactionsResult> </QueryTransactionsResponse> </soap:body> Response with no transaction data <soap:body> <QueryTransactionsResponse xmlns=" <QueryTransactionsResult/> </QueryTransactionsResponse> </soap:body> Failed Response It will throw exception if there is any login error or data type error.
31 Appendix D: Test procedures Testing details Please make sure you use the following values when testing; Test gateway - Test Customer ID Test Username test@eway.com.au Test Password test123 Test Credit Card Number Please note that if you try to query customer, rebill event or transaction details, the test gateway will only return the mockup data.
Token Payment Web Services
Web Active Corporation/eWAY Token Payment Web Services Data type and field specifications 23/06/2010 Version 1.4 Contents Introduction... 3 Data Field Specifications... 4 Field Description... 6 Validation
eway AU Hosted Payment Page
Web Active Corporation eway AU Hosted Payment Page Full Analysis and Data Type Field Specifications Contents Introduction... 3 Customisation... 4 Processing Fraud Protected Transactions... 5 Appendix A
Recurring Payments Manual
Recurring Payments Manual Version: 3.2 Contact details Simon Carmiggeltstraat 6-50 1011 DJ Amsterdam P.O. Box 10095 1001 EB Amsterdam The Netherlands T +31 20 240 1240 E support@adyen.com Table of Contents
Microsoft Active Directory Oracle Enterprise Gateway Integration Guide
An Oracle White Paper May 2011 Microsoft Active Directory Oracle Enterprise Gateway Integration Guide 1/33 Disclaimer The following is intended to outline our general product direction. It is intended
Secure XML API Integration Guide - Periodic and Triggered add in
Secure XML API Integration Guide - Periodic and Triggered add in Document Control This is a control document DESCRIPTION Secure XML API Integration Guide - Periodic and Triggered add in CREATION DATE 15/05/2009
Freight Tracking Web Service Implementation Guide
www.peninsulatruck.com P.O. Box 587 (98071-0587) 1010 S 336 th, Suite 202 Federal Way, Washington 98003 Office (253) 929-2000 Fax (253) 929-2041 Toll Free (800) 942-9909 Freight Tracking Web Service Implementation
Bank and SecurePay Response Codes
Bank and SecurePay s Last updated: 19/07/2013 Bank s for Credit Card Transactions APPROVED 00 Approved 08 Honour with ID 11 Approved VIP (not used) 16 Approved, Update Track 3 (not used) 77 Approved (ANZ
Using ilove SharePoint Web Services Workflow Action
Using ilove SharePoint Web Services Workflow Action This guide describes the steps to create a workflow that will add some information to Contacts in CRM. As an example, we will use demonstration site
PAYLINE USER GUIDE LOGGING INTO PAYLINE PROCESSING A PURCHASE
Payline User Guide PAYLINE USER GUIDE Payline is a web-based payment management client that can be used to process credit card transactions manually, process refunds, set up recurring payments and generate
PathwayLINK Recurring Billing Document Version 1.7 Published NOV 2011
PathwayLINK Recurring Billing Document Version 1.7 Published NOV 2011 Email: developersupport@tgatepayments.com T-Gate, LLC 1821 Walden Square Suite 220 Schaumburg, IL 60173 www.tgatepayments.com PathwayLINK
GATEWAY FREEDOM INTEGRATION GUIDE
Payment solutions for online commerce GATEWAY FREEDOM INTEGRATION GUIDE Copyright PayPoint.net 2010 This document contains the proprietary information of PayPoint.net and may not be reproduced in any form
Merchant Interface Online Help Files
Merchant Interface Online Help Files REGAL t e c h n o l o g i e s t h e f u t u r e o f p a y m e n t s Table of Contents Merchant Interface Online Help Files... 1 Tools... 2 Virtual Terminal... 7 Submit
Version: 1. Cellfind_MPG SDK Technical Specification
Cellfind SDK Technical Specification Version: 1 Filename: Cellfind_MPG SDK Technical Specification Last Revision Date: 09/10/2014 Contents WEB SERVICE QA AND LIVE URL ADDRESSES... ERROR! BOOKMARK NOT DEFINED.
PAYLINE USER GUIDE. 1 Logging into Payline. 2 - Processing a Purchase
PAYLINE USER GUIDE Payline is a web-based payment management client that can be used to process credit card transactions manually, process refunds, set up recurring payments and generate reports to name
GoCoin: Merchant integration guide
GoCoin: Merchant integration guide More information can be found at help.gocoin.com Preface This guide is intended for Merchants who wish to use the GoCoin API to accept and process payments in Cryptocurrency.
e Merchant Plug-in (MPI) Integration & User Guide
Payment solutions for online commerce e Merchant Plug-in (MPI) Integration & User Guide Enabling merchants to integrate their payment processing with PayPoint.net s 3D Secure Merchant Plug In (MPI) solution.
The BritNed Explicit Auction Management System. Kingdom Web Services Interfaces
The BritNed Explicit Auction Management System Kingdom Web Services Interfaces Version 5.1 November 2014 Contents 1. PREFACE... 6 1.1. Purpose of the Document... 6 1.2. Document Organization... 6 2. Web
TARGETPROCESS WEB SERVICES GUIDE
TARGETPROCESS WEB SERVICES GUIDE v.2.10 Web Services API / Developers Guide This document describes Web Services in TargetProcess and provides some usage examples. 1 TARGETPROCESS DOMAIN MODEL... 3 PROJECT...
It is most commonly used by organizations that require a cost effective, quick, simple process for accepting credit card payments.
0 Payline 1 Overview Payline is a web-based client that can be used to process credit card transactions manually, process refunds, set up recurring payments and generate reports to name a few of its functions.
2Checkout Instant Notification Service User Guide Changes Revision 1.0 to 1.1
INS User Guide Changes 2Checkout Instant Notification Service User Guide Changes Table of Contents Overview...2 Messages Supported...2 Message Changes...2 New Messages...2 Message Parameters...2 New Values
Trupointe Cooperative On Line Payment by Credit Card Procedure for Customers Original Date: 10/19/12 Revised Date: 11/18/13
Log onto www.trupointe.com Website Click on My Account Login Click on Make A Payment You can choose to either Register or Pay Without Registering To Pay Without Registering, skip to Page 4 Page 1 of 6
Recurring Payments Service (FuturePay) Guide. Version 4.2 April 2013 Business Gateway
Recurring Payments Service (FuturePay) Guide Version 4.2 April 2013 Business Gateway Table Of Contents About this Guide... 4 Update History... 4 Copyright... 4 Introduction... 5 Enable the Service... 6
INTEGRATION PROCEDURES AND SPECIFICATIONS
ipos Credit Card Payment Gateway INTEGRATION PROCEDURES AND SPECIFICATIONS Revision 7 Contents Contents 2 Introduction 3 ipos the simple online credit card solution 3 The Transaction Flow 4 Security 7
Payment Page Extensions. Online Payment Processing for Businesses Worldwide. www.telr.com
Payment Page Extensions Online Payment Processing for Businesses Worldwide www.telr.com Page 2 of 13 Contents About this guide... 3 Copyright... 3 Introduction... 3 Using an extension... 4 Additional information
SPARROW Gateway. Developer API. Version 2.00
SPARROW Gateway Developer API Version 2.00 Released May 2015 Table of Contents SPARROW Gateway... 1 Developer API... 1 Overview... 3 Architecture... 3 Merchant Private Key and Payment Types... 3 Integration...
Merchant Interface Online Help Files
Merchant Interface Online Help Files Table of Contents Merchant Interface Online Help Files... 5 Tools... 6 Virtual Terminal... 7 Submit a Credit Card Charge... 7 Submit a Credit Card Refund... 9 Submit
WEB TERMINAL AND RECURRING BILLING
PROCESSING TRANSACTIONS WITH WEB TERMINAL AND RECURRING BILLING Document Version 1.4 December 2013 For further information please contact Digital River customer support at 0800 756 3350 or clientsupport.uk@digitalriver.com.
Last Modified June 2008
Payment Gateway Virtual Terminal Last Modified June 2008 E-Business the easy way! Website: www.vcs.co.za Contact: +27 (0) 11 257 6222 E-mail: sales@vcs.co.za Virtual Card Services (Pty) Ltd Registration
Sage CRM. Sage CRM 2016 R1 Web Services Guide
Sage CRM Sage CRM 2016 R1 Web Services Guide Copyright 2015 Sage Technologies Limited, publisher of this work. All rights reserved. No part of this documentation may be copied, photocopied, reproduced,
Batch Processing Version 2.0 Revision Date: April 29, 2014
Batch Processing Version 2.0 Revision Date: April 29, 2014 1 Processing payments with batch files is very simple: 1. You put your payment records into tab-delimited text files. In this format, data items
Credomatic Integration Resources. Browser Redirect API Documentation June 2007
Credomatic Integration Resources Browser Redirect API Documentation June 2007 Table of Contents Methodology... 2 Browser Redirect Method (Browser to Server) FIG. 1... 2 API Authentication Parameters...
Web-Service Example. Service Oriented Architecture
Web-Service Example Service Oriented Architecture 1 Roles Service provider Service Consumer Registry Operations Publish (by provider) Find (by requester) Bind (by requester or invoker) Fundamentals Web
SFTP Batch Processor. Version 1.0
SFTP Batch Processor Version 1.0 CONTENTS 1. OVERVIEW... 2 2. SFTP CONNECTION... 3 3. INPUT FILE SPECIFICATION... 4 4. OUTPUT FILE SPECIFICATION... 6 5. BATCHING SCENARIOS... 8 7. MESSAGE FIELD PROPERTIES...
Skipjack Merchant User Guide. Quick Guide. (a supplement to the Merchant User Guide)
Skipjack Merchant User Guide Quick Guide (a supplement to the Merchant User Guide) COPYRIGHT INFORMATION Evolve Adaptive Technology and Skipjack Financial Services are registered trademarks of the Bradley-Madison
GetFormatList. Webservice name: GetFormatList. Adress: https://www.elib.se/webservices/getformatlist.asmx
GetFormatList Webservice name: GetFormatList Adress: https://www.elib.se/webservices/getformatlist.asmx WSDL: https://www.elib.se/webservices/getformatlist.asmx?wsdl Webservice Methods: Name: GetFormatList
Payment Gateway HTTP and XML API Developers Documentation. HTTP/XML API 1.2.0 Last Modified: 28 September 2015
Payment Gateway HTTP and XML API Developers Documentation HTTP/XML API 1.2.0 Last Modified: 28 September 2015 Preface This document supersedes any previous documentation on the GSPAY Payment Gateway XML
Merchant One Payment Systems Integration Resources. Direct Post API Documentation June 2007
Merchant One Payment Systems Integration Resources Direct Post API Documentation June 2007 Table of Contents Methodology... 2 Direct Post Method (Server to Server) FIG. 1... 2 Transaction Types... 3 Sale
Merchant Web Services API
Title Page Merchant Web Services API Automated Recurring Billing (ARB) SOAP Guide December 2015 Authorize.Net Developer Support http://developer.authorize.net Authorize.Net LLC 082007 Ver.2.0 Authorize.Net
Virtual Terminal Introduction and User Instructions
Virtual Terminal Introduction and User Instructions Trine Commerce Systems, Inc. 2613 Wilson Street Austin, TX 78704 512-586-2736 legal@trinecs.com techsupport@trinecs.com Legal Notice All content of this
HTS SOLAR PANELS. Save On Energy, Save the Planet. Tom Stuck Jacob Hernandez Reese Trotter
HTS SOLAR PANELS HTS SOLAR PANELS Save On Energy, Save the Planet Tom Stuck Jacob Hernandez Reese Trotter Page 0 HTS SOLAR PANELS S AV E O N E N E R G Y, S AV E T H E P L A N E T TABLE OF CONTENTS Site
How To Use The Elavon Payment Gateway Virtual Terminal On A Credit Card Over The Phone
Elavon Payment Gateway- Virtual Terminal User Guide Version: v1.0 Page 1 Table of Contents 1 About This Guide 3 1.1 Purpose 3 1.2 Audience 3 1.3 Related Documents 3 1.4 Terminology 4 1.5 Conventions 5
Elavon Payment Gateway- Reporting User Guide
Elavon Payment Gateway- Reporting User Guide Version: v1.1 Contents 1 About This Guide... 4 1.1 Purpose... 4 1.2 Audience... 4 1.3 Prerequisites... 4 1.4 Related Documents... 4 1.5 Terminology... 4 1.6
PINless Debit Card Services
Title Page PINless Debit Card Services Using the SCMP API September 2015 CyberSource Corporation HQ P.O. Box 8999 San Francisco, CA 94128-8999 Phone: 800-530-9095 CyberSource Contact Information For general
Title: ematters Integration API Specification. Product of: ematters Australia Pty Ltd. Version: 2.0 ABN: 46 066 323 582. Date: 6 August 2012
Product of: ematters Australia Pty Ltd Title: ematters Integration API Specification ABN: 46 066 323 582 Version: 2.0 Date: 6 August 2012 ematters Integration API Specification Contents 1 Document Control...
CyberSource Merchant Account Reports
Title Page CyberSource Merchant Account Reports Developer Guide July 2015 CyberSource Corporation HQ P.O. Box 8999 San Francisco, CA 94128-8999 Phone: 800-530-9095 CyberSource Contact Information For general
SPARROW Gateway. Developer Data Vault Payment Type API. Version 2.7 (6293)
SPARROW Gateway Developer Data Vault Payment Type API Version 2.7 (6293) Released July 2015 Table of Contents SPARROW Gateway... 1 Developer Data Vault Payment Type API... 1 Overview... 3 Architecture...
Secure XML API Integration Guide. (with FraudGuard add in)
Secure XML API Integration Guide (with FraudGuard add in) Document Control This is a control document DESCRIPTION Secure XML API Integration Guide (with FraudGuard add in) CREATION DATE 02/04/2007 CREATED
Network Merchants Inc (NMI) Integration Resources. Direct Post API Documentation April 2010
Network Merchants Inc (NMI) Integration Resources Direct Post API Documentation April 2010 Table of Contents Methodology... 2 Direct Post Method (Server to Server) FIG. 1... 2 Transaction Types... 3 Sale
Cvent Web Services API. Version V200611 June 2008
Cvent Web Services API Version V200611 Cvent, Inc. 8180 Greensboro Dr, Suite 450 McLean, VA 22102 866.318.4357 www.cvent.com customercare@cvent.com 1.0 Framework Overview... 1 1.1 Overview... 1 1.2 Compatible
Merchant Web Services API
Merchant Web Services API Automated Recurring Billing (ARB) XML Guide Authorize.Net Developer Support http://developer.authorize.net Authorize.Net LLC 042007 Ver.1.0 Authorize.Net LLC ( Authorize.Net )
Rapid 3.0 Transparent Redirect API. Official eway Documentation. Version 0.82
Rapid 3.0 Transparent Redirect API Official eway Documentation Version 0.82 Published on 8/08/2013 Contents Welcome from eway CEO... 5 Overview... 6 Payment types included... 7 Individual payments... 7
API documentation - 1 -
API documentation - 1 - Table of Contents 1. Introduction 1.1. What is an API 2. API Functions 2.1. Purge list of files 2.1.1 Description 2.1.2 Implementation 2.2. Purge of whole cache (all files on all
Implementation guide Web Services V4. Version 1.4b
Implementation guide Web Services V4 Version 1.4b Confidentiality All the information in the current document is considered confidential. Using it outside the context of this consultation or disclosing
Recurring Billing. Using the SCMP API. October 2015. CyberSource Corporation HQ P.O. Box 8999 San Francisco, CA 94128-8999 Phone: 800-530-9095
Title Page Recurring Billing Using the SCMP API October 2015 CyberSource Corporation HQ P.O. Box 8999 San Francisco, CA 94128-8999 Phone: 800-530-9095 CyberSource Contact Information For general information
Teiid - Salesforce Connector Guide 6.2.0
Teiid - Salesforce Connector Guide 1 6.2.0 Preface... v 1. Importing Metadata... 1 1.1. Overview... 1 1.2. Running the Importer... 1 2. Using the Connector... 7 2.1. SQL Processing... 7 2.2. Selecting
Skipjack VPOS User Guide
Skipjack VPOS User Guide Skipjack 2230 Park Avenue Cincinnati, OH 45206 www.skipjack.com User Guide Table of Contents Click on a topic below to view its contents. Logging in to Your Account p. 3 Launch
I. Simplifying Payment Processing. II. Authorizing Your Transactions Correctly page 6
Welcome to PaySimple! Congratulations on choosing PaySimple for all your payment processing needs! You will quickly notice that billing and collections is transformed into an effortless process. With PaySimple,
Recurring Billing. Using the Simple Order API for CyberSource Essentials. March 2016
Title Page Recurring Billing Using the Simple Order API for CyberSource Essentials March 2016 CyberSource Corporation HQ P.O. Box 8999 San Francisco, CA 94128-8999 Phone: 800-530-9095 CyberSource Contact
United Payment Services My Merchant Console Connect Virtual Terminal User Guide
United Payment Services My Merchant Console Connect Virtual Terminal User Guide. 1 United Payment Services, Inc ( United Payment Services ) has made efforts to ensure the accuracy and completeness of the
GFI FaxMaker Online Inbound Web Services V.1.0
GFI FaxMaker Online Inbound Web Services V.1.0 Publication Notice The contents of this publication the specifications of this application are subject to change without notice. GFI Software reserves the
Report Builder CRM Reporting Model
Report Builder CRM Reporting Model The CRM reporting model allows you to retrieve all company, contact and associated project data via Microsoft Report Builder. The following is a guide to all of the entities
WebAddress Domain Registrar
WebAddress Domain Registrar Introduction WebAddress (http://www.webaddress.co.nz) is a New Zealand domain name registrar. We provide our Members with the tools to effectively manage your own domain names
Dev Guide for Encrypted Swipe
Dev Guide for Encrypted Swipe Version 1.5 Last Updated: 20 th August 2014 Table of Contents 1 Introduction... 3 2 Important notes... 4 3 Concept Overview... 5 4 Encrypted Swipe Devices... 6 4.1 Magtek
United Concordia (UCD) Real Time Claim Submission & Adjudication Connectivity Specifications
United Concordia (UCD) Real Time Claim Submission & Adjudication Connectivity Specifications May 15, 2015 Contents 1. Real Time Overview 2. Requirements 3. SOAP Messages 4. SOAP Faults 5. CORE-Compliant
GSPAY Merchant Manual
GSPAY Merchant Manual Version 1.6.2 Last Updated: 4 March 2013 All material contained herein is Copyright GSPAY LIMITED. Please report any errors or omissions in this documentation to the GSPAY support
Web Services Credit Card Errors A Troubleshooter
Web Services Credit Card Errors A Troubleshooter March 2011 This manual and accompanying electronic media are proprietary products of Optimal Payments plc. They are to be used only by licensed users of
Volume PLANETAUTHORIZE PAYMENT GATEWAY. vtiger CRM Payment Module. User Guide
Volume 2 PLANETAUTHORIZE PAYMENT GATEWAY vtiger CRM Payment Module User Guide S A L E M A N A G E R M E R C H A N T S E R V I C E S User Guide and Installation Procedures Information in this document,
Durango Merchant Services Customer Vault API
Durango Merchant Services Customer Vault API V1.1 Integration Resources Documentation April 2008 Updated Sept 2011 Durango-Direct.com 866-415-2636 Contents Overview... 3 Customer Vault... 3 Methodology...
EMAIL EDITOR & SITE TAGS
Feature Overview & Tutorial EMAIL EDITOR & SITE TAGS Create & Assign HTML Email Templates Overview Email Editor & Site Tags The Email Editor gives you the ability to use the email templates we provide,
e-filing Secure Web Service User Manual
e-filing Secure Web Service User Manual Page1 CONTENTS 1 BULK ITR... 6 2 BULK PAN VERIFICATION... 9 3 GET ITR-V BY TOKEN NUMBER... 13 4 GET ITR-V BY ACKNOWLEDGMENT NUMBER... 16 5 GET RETURN STATUS... 19
GettingStarted. ProjectRequirementsChecklist. w e b s o l u t i o n s. off (yes/no) Store Name: Store Address:* Phone: Fax: Generic Email Address:**
GettingStarted COMPANY: 1 Sign FLOW CHART off (yes/no) PROJECT AGREEMENT 2 Store STORE DETAILS Owner: Store Name: Sign off (yes/no) DEPOSIT Sent (yes/no) Store Address:* Phone: Fax: Generic Email Address:**
Informatica Cloud Connector for SharePoint 2010/2013 User Guide
Informatica Cloud Connector for SharePoint 2010/2013 User Guide Contents 1. Introduction 3 2. SharePoint Plugin 4 3. Objects / Operation Matrix 4 4. Filter fields 4 5. SharePoint Configuration: 6 6. Data
Monetra Payment System
Monetra Payment System Table of Contents 1 Secure Storage and Billing System Overview 1.1 Introduction 1.2 Storage Overview 1.3 Billing Overview 2 Installation and Configuration 2.1 New System Installation
Cofred Automated Payments Interface (API) Guide
Cofred Automated Payments Interface (API) Guide For use by Cofred Merchants. This guide describes how to connect to the Automated Payments Interface (API) www.cofred.com Version 1.0 Copyright 2015. Cofred.
Middleware and the Internet
Middleware and the Internet Middleware today Designed for special purposes (e.g. DCOM) or with overloaded specification (e.g. CORBA) Specifying own protocols integration in real world network? Non-performant
CyberSource Business Center
CyberSource Business Center CS-5-123110 Copyright 2010 Harris Connect, LLC. all rights reserved. Reproduction in any form without the express written consent of Harris Connect, LLC. is strictly prohibited
Gateway Direct Post API
Gateway Direct Post API http://merchantguy.com @MerchantGuy Questions? info@merchantguy.com Contents Methodology....3! Direct Post Method (Server to Server FIG. 1...3 Transaction Types.....4! Sale (sale)..4!
Mobile Web Payment Models ( implementations)
mcharge mobile-web payments Interface Specifications Version 1.1.2 31/05/2011 31/05/2011-2/11 1. Revisions Rev# Date Remark 1.0 07-04-2008 Initial version 1.1 21-04-2008 Adding advanced parameters to the
Magensa Services. Administrative Account Services API Documentation for Informational Purposes Only. September 2014. Manual Part Number: 99810058-1.
Magensa Services Administrative Account Services API Documentation for Informational Purposes Only September 2014 Manual Part Number: 99810058-1.01 REGISTERED TO ISO 9001:2008 Magensa I 1710 Apollo Court
Getting Started with Swipe Checkout
Getting Started with Swipe Checkout What s Inside Hi! So you re all signed up as a Swipe Checkout merchant and the way you sell online is going to be easier than ever before. In this guide we are going
Internet Payment Gateway
Internet Payment Gateway Merchant Administration Console Merchant Services TABLE OF CONTENTS Introduction to the Merchant Administration Console... 5 Console Overview... 5 Login Conditions... 5 Merchant
Easy CollECt and the transaction ManagEr interface
Easy Collect and the Transaction Manager Interface Table of Contents 1 2 3 Easy Collect... 4 1.1. Configuring your account for Easy Collect... 4 1.1.1. Creating your Easy Collect ID... 4 1.1.1.1. Transaction
ANZ egate Merchant Administration. Quick Reference Guide
ANZ egate Merchant Administration Quick Reference Guide Purpose The purpose of this Quick Reference Guide is to provide the user with a quick reference to using the ANZ egate Merchant Administration. We
Hosted Credit Card Forms Implementation Guide
Hosted Credit Card Forms Implementation Guide Merchant implementation instructions to integrate to the Setcom s hosted credit card forms. Covers: fraud screening, Verified by Visa, MasterCard SecureCode
SecurePay Batch File Specification & Upload Procedure
SecurePay Batch File Specification & Upload Procedure Document Control Description SecurePay Batch File Specification & Upload Procedure Creation Date 18/08/2009 Created By SecurePay Version 1.6 Date updated
Architecture and Data Flow Overview. BlackBerry Enterprise Service 10 721-08877-123 Version: 10.2. Quick Reference
Architecture and Data Flow Overview BlackBerry Enterprise Service 10 721-08877-123 Version: Quick Reference Published: 2013-11-28 SWD-20131128130321045 Contents Key components of BlackBerry Enterprise
Replacements TECHNICAL REFERENCE. DTCCSOLUTIONS Dec 2009. Copyright 2009 Depository Trust Clearing Corporation. All Rights Reserved.
TECHNICAL REFERENCE Replacements Page 1 Table of Contents Table of Contents 1 Overview... 3 1.1 Replacements Features... 3 2 Roles and Responsibilities... 4 2.1 Sender (Receiving Carrier)... 4 2.2 Recipient
Virtual Terminal & Online Portal
Authipay Gateway Virtual Terminal & Online Portal User Guide Version 5 (EMEA) Virtual Terminal & Online Portal User Guide Version 5 (EMEA) CONTENTS 1 Introduction... 5 2 Processing Transactions... 6 2.1
Merchant Administration
Merchant Administration User Guide Version 4.2.0 For TNSPay 4.2 Disclaimer Copyright 2010 TNS Payment Technologies Pty Ltd ("TNS"). All rights reserved. This document is provided by TNS on the basis that
Oracle Web Service Manager 11g Field level Encryption (in SOA, WLS) March, 2012
Oracle Web Service Manager 11g Field level Encryption (in SOA, WLS) March, 2012 Step-by-Step Instruction Guide Author: Prakash Yamuna Senior Development Manager Oracle Corporation Table of Contents Use
REST Webservices API Reference Manual
crm-now/ps REST Webservices API Reference Manual Version 1.5.1.0 crm-now development documents Page 1 Table Of Contents OVERVIEW...4 URL FORMAT...4 THE RESPONSE FORMAT...4 VtigerObject...5 Id Format...5
Safeguard Ecommerce Integration / API
Safeguard Ecommerce Integration / API Product Manual Version 3 Revision 1.11 Table of Contents 1. INTRODUCTION... 4 1.1 Available commands... 4 2. HOW THE ADMINISTRATION SYSTEM IS EXPECTED TO BE USED OPERATIONALLY...
Web Services Credit Card Errors A Troubleshooter
Web Services Credit Card Errors A Troubleshooter January 2012 This manual and accompanying electronic media are proprietary products of Optimal Payments plc. They are to be used only by licensed users
Gateway Integration Specifications Credit Card Processing
Gateway Integration Specifications Credit Card Processing Version 3.2 Trine Commerce Systems, Inc. 2613 Wilson Street Austin, TX 78704 512-586-2736 legal@trinecs.com techsupport@trinecs.com Legal Notice
ipay Checkout API (IPC API)
ipay Checkout API (IPC API) Accepting e-commerce payments for merchants Version 2.1 Intercard Finance AD 2007 2013 Table of Contents Introduction... 9 Scope... 10 the merchant / commercial decision makers...
Three Step Redirect API V2.0 Patent Pending
Three Step Redirect API V2.0 Patent Pending Contents Three Step Redirect Overview... 4 Three Step Redirect API... 4 Detailed Explanation... 4 Three Step Transaction Actions... 7 Step 1... 7 Sale/Auth/Credit/Validate/Offline
SoftwarePlanner Active Directory Authentication
User s Guide SoftwarePlanner Active Directory Authentication This document provides an explanation of using Active Directory with SoftwarePlanner. 1 Narrative In some situations, it may be preferable to
Credit Card Retrieval API Implementation Guide This guide illustrates how to implement the Credit Card Retrieval API.
Credit Card Retrieval API Implementation Guide This guide illustrates how to implement the Credit Card Retrieval API. Copyright: Jumio Inc. 268 Lambert Avenue, Palo Alto, CA 94306 Contents Credit Card
Payvision Payment Processor. Technical Integration
Payvision Payment Processor Technical Integration Rights of use: COMPLYING WITH ALL APPLICABLE COPYRIGHT LAWS IS THE RESPONSABILITY OF THE USER. WITHOUT LIMITING THE RIGHTS UNDER COPYRIGHT, NO PART OF