Getting Started

Introduction

Guides lay down the core requirements to accept and manage payments though the ECRYPT API. You will have a better understanding of how to implement the following functions:

• Accept card-present transactions
• Accept card-not-present transactions
• Tokenization
• Store and manage customers
• Build custom payment flows
• Testing integrations

Every transaction runs through ECRYPT's payment flow designed to make transactions fast and secure. Transactions must begin with tokenization in order to keep sensitive cardholder data protected. Tokenization also helps to remove PCI scope for software applications using ECRYPT's API.

Payment flow for standard transaction:

[]

What you will need

Test Account
To get started you will need to set up a test account. Test accounts allow you to explore ECRYPT's functionality and test your workflows with dummy credit card numbers and checking account numbers.

Click here to sign up here for a test account

API Key
After you have your test or production account you will need to generate an API key to integrate with ECRYPT.

Create your API keys in Settings > API/Security Keys

[]

Public IP Addresses

Use these IPs to allowlist ECRYPT's servers for webhooks and inbound API traffic.

52.26.189.58
44.232.175.238
44.224.200.173
52.33.202.58

Implementation

Reference the Card Present Integration Guide for accepting in-person payments with ECRYPT's Cloud EMV devices.

Reference the Card Not Present Integration Guide for accepting payments online with solutions like hosted iFrame, invoicing, subscriptions and hosted payments pages.

Supported Payment Methods:

• Visa
• MasterCard
• American Express
• Discover
• ACH Bank Transfer
• Cash

Certification to go live

Certification
Your implementation must be tested and certified by ECRYPT before going live. We recommend testing the following payment flows prior to your certification:

• Sale
• Refund
• Void
• Authorization only
• Authorization, capture
• Authorization, void
  Certification requirements vary depending on the type of integration and entry points used for accepting payments.

Getting Help

We're standing by to help with your implementation. Visit the resources page to get in touch with our developer support team.