SysPay Implementation Guide

Table of contents

• 1. Processing API (for merchants)
  • 1.1. Introduction
    • 1.1.1. Pre-conditions to use the SysPay API
    • 1.1.2. Sandbox and live system
  • 1.2. API Methods
    • 1.2.1. Authentication
    • 1.2.2. Errors
    • 1.2.3. Hosted payment request
    • 1.2.4. Server-to-server payment request
    • 1.2.5. Paying out to other accounts
    • 1.2.6. Post-payment redirection
    • 1.2.7. Get payment information
    • 1.2.8. Get a list of payments
    • 1.2.9. Get a list of operations
    • 1.2.10. Confirm a pre-authorization
    • 1.2.11. Void a pre-authorization
    • 1.2.12. Make a refund
    • 1.2.13. Get refund information
    • 1.2.14. Get a list of refunds
    • 1.2.15. Get billing agreement information
    • 1.2.16. Get a list of billing agreements
    • 1.2.17. Cancel a billing agreement
    • 1.2.18. Issue a rebill on a billing agreement
    • 1.2.19. Get chargeback information
    • 1.2.20. Get a list of chargebacks
    • 1.2.21. Get system ip addresses
    • 1.2.22. Get a list of Astropay banks
    • 1.2.23. Get a list of iDeal banks
    • 1.2.24. Paying out to other accounts
  • 1.3. eMerchant Subscription API
    • 1.3.1. Definitions
    • 1.3.2. Subscription lifecycle
    • 1.3.3. Create a plan
    • 1.3.4. Update a plan
    • 1.3.5. Subscribe a customer to a plan (hosted flow)
    • 1.3.6. Subscribe a customer to a plan (server-2-server flow)
    • 1.3.7. Subscribe a customer to a plan by re-using an existing subscription or billing agreement
    • 1.3.8. Issue a manual rebill on a subscription
    • 1.3.9. Cancelling a subscription
  • 1.4. eTerminal API
    • 1.4.1. Requesting an eTerminal instance
    • 1.4.2. Locking the form inputs
  • 1.5. Client-side tokenization (JS)
    • 1.5.1. Client-side requirements
    • 1.5.2. Callback
    • 1.5.3. Sample HTML page
    • 1.5.4. Using it with our API
  • 1.6. eMerchant Event Messaging System (EMS)
    • 1.6.1. EMS message content
    • 1.6.2. EMS callback validation
    • 1.6.3. Event types
  • 1.7. Statuses and codes
    • 1.7.1. Payment statuses
    • 1.7.2. Payment types
    • 1.7.3. Failure categories
    • 1.7.4. Subscription statuses
    • 1.7.5. Subscription end reasons
    • 1.7.6. Subscription phases
    • 1.7.7. Subscription events
    • 1.7.8. Operation types
    • 1.7.9. Operation status
    • 1.7.10. Error Codes
  • 1.8. Testing
    • 1.8.1. General guidelines
    • 1.8.2. Creditcard payments
    • 1.8.3. iDEAL payments
• 2. Partner API
  • 2.1. Partner Referral URL Generation
    • 2.1.1. Example code (PHP)
  • 2.2. Partner Event Messaging System (EMS)
    • 2.2.1. EMS message content
    • 2.2.2. EMS callback validation
    • 2.2.3. Event types