Integration options

This section provides answers to the most common questions about additional solutions for application and system integrations.

How difficult is it to integrate with InCountry products?

Our company offers different kinds of products which can be integrated into your existing software solutions for data residency services. They mainly differ in integration efforts from your side, as follows:

1. InCountry Border requires minimal integration efforts from your side. You just need to proxy your requests from the application frontend to InCountry Border and that’s all. It requires additional configuration and deployment by the InCountry team. It provides the server-side encryption and provides the capabilities available in InCountry Border, but does not require changes in the code base of your application.

2. InCountry REST API requires more integration efforts from your side as you need to modify your application codebase, but as an advantage, you get the server-side encryption. You do not need to worry about where to keep the encryption key, how to use it, and so on. Our team will elaborate on all this. You just need to receive a certificate and use it while performing data requests from the application frontend. It requires additional configuration and deployment by the InCountry team.

3. InCountry SDK requires additional integration efforts from your side, as you need to fully integrate it into your application code base and keep the encryption keys. It provides maximum freedom in the implementation of data residency solutions for your business cases. You need to choose InCountry SDK in the following situations:

   1. You need full control over the key.
   2. You need to use some other encryption method.
   3. You do not want InCountry to deal anyhow with your encryption key.
   4. You want to customize InCountry SDK for your production needs.

4. InCountry Integrations provide the native integration with SaaS solutions in the service-specific format (a specific token format, data request structure, and so on).

What integration options does InCountry Platform offer?

InCountry Platform also provides additional solutions for application and system integrations, as follows:

• Mail Proxy
• Report Proxy
• SFTP Proxy
• Payment Gateway

Mail Proxy

This solution allows you to unredact regulated data in emails by sending them to the InCountry SMTP Proxy server. It parses data, unredacts it, and sends further to the required addressees. You can use the Mail Proxy to send notifications about events and actions within your application, for example, event notifications in Salesforce.

Report Proxy

This solution allows you to unredact regulated data when generating reports in some SaaS solution. It fetches redacted data from InCountry and replaces tokenized data with actual values in different types of reports or reporting files of yours. It has limited capabilities and depends on the reporting mechanism, which is used by a particular SaaS solution.

SFTP Proxy

This solution allows you to unredact data transferred through the SFTP protocol and redacts/unredacts data in the source files before passing it further into the workflow.

Payment Gateway

This solution allows you to handle the payment data (cardholder and card details) and pass it to the payment provider (for example, Stride) while saving this data to InCountry Platform. It redacts the card information on the fly and allows you to process payments through your server and being PCI-DSS compliant at the same time.

You can use it for one-time and recurrent payments, as well as for making subscriptions.

This component provides the payment web form which collects the payment details, writes this data to InCountry Platform, and further provides this payment data to a specific payment provider for performing a transaction.

This product allows you to develop a single payment gateway application that will be compatible with multiple payment providers in different countries without a necessity to be PCI-DSS compliant for keeping the cardholder information.

Other specifics

You cannot use InCountry REST API (with backend) and InCountry SDK, as unredacted data should not reach your application backend which InCountry SDK integrates with.

Additionally, you can use InCountry Serverless when you need to perform additional data processing in the country where you want to store this regulated data. For example, some complex validation like checking the uniqueness of the entered email address in your application database. You can create a serverless function that runs a query against this email to InCountry Platform in the origin country and validates the uniqueness of the provided email address. If invalidated, the email address will be rejected by your application.