Ingenico Direct Support Site

Results for

icon-search-large No search results yet
Enter your search query above

Introduction

To understand how to use this SDK it is best to read the following documentation:

  • Server Introduction
    First read the Server Introduction to familiarize yourself with the various concepts.
  • Server API Reference
    This Server SDK wraps the Server API and (amongst other things) exposes the responses of the webservice calls as .NET objects. Understanding the Server API will help you understanding these SDK objects as well.
  • This current document will help you understand the global flow when interacting with the Ingenico Direct platform using the .NET SDK.

The .NET SDK helps you to communicate with the Server API. More specifically, it offers a fluent .NET API that provides access to all the functionality of the RESTful Server API. Below, we discuss the following topics in detail.

The source code of the SDK is available on Github. There you can find installation instructions.

Initialization of the .NET SDK

All C# code snippets presented in the API reference assume you have initialized the .NET SDK before using them in your Development Environment. This section details the initialization of the .NET SDK.

Initializing is simple, and requires only one key task: use our Factory class to create an instance of IClient, which contains the actual methods to communicate with the Server API.

The Factory needs the following input information to provide you with an initialized IClient.

  • An IDictionary<string,string> containing your connection configuration
  • The secretApiKey and apiKeyId. The secretApiKey is a key that is used to authenticate your API requests, and apiKeyId identifies that key (as you can have multiple active keys). Both of these can be obtained from the Ingenico Direct setting tab in the BackOffice.

Your IDictionary should have the following entries:

SDK: .NET

{"direct.api.integrator", "<your company name>"},
{"direct.api.endpoint.host", "api.domain.com"},
// The entries below are optional and use the given value by default
{"direct.api.endpoint.scheme", "https"},
{"direct.api.endpoint.port", "-1"},
{"direct.api.authorizationType", "V1HMAC"},
{"direct.api.connectTimeout", "10"},
{"direct.api.socketTimeout", "10"},
{"direct.api.maxConnections", "10"}

See API endpoints for the possible hosts.

If a proxy should be used, your IDictionary should also include these proxy properties:

SDK: .NET

{"direct.api.proxy.uri", "<URL to the proxy host, including leading http(s)://>"},
// omit the following two properties if no proxy authentication is required.
{"direct.api.proxy.username", "<username for the proxy>"},
{"direct.api.proxy.password", "<password for the proxy>"}

You can create an instance of IClient using the Factory with this code snippet:

SDK: .NET
IClient client = Factory.CreateClient(dictionary, "apiKeyId", "secretApiKey");

This IClient instance offers connection pooling and can be reused for multiple concurrent API calls. Once it is no longer used it should be closed.

IClient implements System.IDisposable, which allows it to be used in using statements.

Client meta information

Optionally, for BI and fraud prevention purposes, you can supply meta information about the client used by the customer. To do so, create a new instance of IClient at the start of the customer's payment process as follows:

SDK: .NET
IClient consumerSpecificClient = client.WithClientMetaInfo("consumer specific JSON meta info");

This consumer-specific instance will use the same connection pool as the IClient from which it was created. As a result, closing an IClient will close all IClient instances created using the WithClientMetaInfo method. There is no need to close these separately.

This closing works both ways. If an IClient created using the WithClientMetaInfo method is closed this will also close the IClient it originated from. This will in turn close all other IClient instances created using the WithClientMetaInfo method. This can be used if only a IClient with client meta info is needed.

Do not use this consumer-specific instance for API calls for other consumers.

Example JSON meta information for a mobile app client:

SDK: .NET
X-GCS-ClientMetaInfo: {
    "platformIdentifier": "Android/4.4",
    "appIdentifier": "Example mobile app/1.1",
    "sdkIdentifier": "AndroidClientSDK/v1.2",
    "screenSize": "800x600",
    "deviceBrand": "Samsung",
    "deviceType": "GT9300",
    "ipAddress": "123.123.123.123"
}

Example JSON meta information for the JavaScript SDK running in a browser:

SDK: .NET
X-GCS-ClientMetaInfo: {
    "platformIdentifier": "Mozilla/5.0 (Linux; U; Android 4.1.1; en-gb; Build/KLP) AppleWebKit/534.30 (KHTML, like Gecko) Version/4.0 Safari/534.30",
    "sdkIdentifier": "JavaScriptClientSDK/v1.2",
    "screenSize": "800x600"
}

Payments

As a merchant, your core interaction with Ingenico Direct typically starts when your customer clicks the checkout button in your application. The payment process usually has the following steps:

  1. Payment Product selection
  2. Setting of available information needed for selected payment product (e.g. amount of the order)
  3. Collection of missing customer information needed for selected payment product (e.g. creditcard number)
  4. Submitting the payment request to the Ingenico Direct platform
  5. Handling the response to the payment request (e.g. payment unsuccessful)

The Ingenico Direct platform offers the following ways of handling this payment process:

  • Use a hosted payment through the Hosted Checkout payment pages
    In this case, you redirect the customer to our hosted payment pages. For you as a merchant, this is the easiest option as the Ingenico Direct platform can handle payment product selection and is responsible for the collection of sensitive data like a creditcard number. Through our Back Office, you still have a lot of control over the look and feel of the checkout.
  • Use a Server SDK to build a payment flow hosted on your server.
    In this case, you can use the Server SDK to obtain the payment products that are applicable to the payment, to obtain the fields that need to be collected from the customer for a selected payment product, and to submit the payment request itself.

In the next couple of paragraphs, we discuss each of these options in more detail.

Use a hosted payment through the Hosted Checkout payment pages (RPP)

The high-level flow of a hosted payment is described below, followed by a more detailed look at each of the steps.

  1. At this point, your customer has provided all relevant information regarding the order, e.g. a shopping cart of items and a shipping address.
  2. See the section on initialization. Use Factory to create an instance of IClient if you hadn't done so yet, and set the meta data that you've collected about the client of the customer.
  3. Create a CreateHostedCheckoutRequest body and populate at least its Order. See the relevant section of the full API reference for more details. You can specify an optional ReturnUrl, which is used to redirect your customer back to your website in step 9.
  4. The create hosted checkout SDK call returns a CreateHostedCheckoutResponse response. Store the hostedCheckoutId and RETURNMAC it contains, as well as any other relevant order information. You will need these when your customer returns from our hosted payment pages, or when the customer fails to return in a reasonable amount of time. This response also contains a partialRedirectURL. You have to concatenate the base URL https://payment. with partialRedirectURL according to the formula https://payment. + partialRedirectURL and perform a redirection of your customer to this URL.
  5. After completing the interactive payment process in the RPP, your customer is redirected back to the url you provided in step 3 as body.HostedCheckoutSpecificInput.ReturnUrl. The HostedCheckoutId and RETURNMAC you stored in step 5 are added to this URL as query parameters. Specifying a ReturnUrl is optional, however. As a result, your customer is only redirected back if you've provided a URL in step 3.
  6. If you cannot identify the customer based on e.g. the HTTP session, you can use the HostedCheckoutId for this purpose. If you do, you must check that the HostedCheckoutId and RETURNMAC from the ReturnUrl match those that you stored in step 3. Note that the RETURNMAC is used as a shared secret between the Ingenico Direct platform and your system that is specific for this hosted checkout.
  7. Retrieve the results of the customer's interaction with the Ingenico Direct platform.
  8. Check the GetHostedCheckoutResponse response returned in step 13. If response.Status equals PAYMENT_CREATED, then the customer attempted a payment, the details of which can be found in response.CreatedPaymentOutput. Depending on the payment product chosen and the status of the payment you can "deliver the goods" immediately, or set up a regular poll of the created payment to wait for the status. Such a poll is done using the SDK call client.Merchant("merchantId").Payments.GetPayment(paymentId), where paymentId is response.CreatedPaymentOutput.Payment.Id. For details on the various payment products and their statuses, see Payment Products.

Additionally, it may be the case that the customer does not return in time (or at all), for example because the browser is closed or because you didn't provide a ReturnUrl. In this case, you need to retrieve the status of the hosted checkout (step 12 of the image above) before the hosted checkout times out, which happens after 2 hours, and follow step 14 of the image above as well.

Use a Server SDK to build a payment flow hosted on your server

The high-level flow of a payment performed from pages hosted on your server is described below, followed by a more detailed look at each of the steps. First, we describe the flow for payment products that do not require a redirect to a payment method hosted by a third party. Afterwards, the flow for payment methods that require a redirect is described.

  1. At this point, your customer has provided all relevant information regarding the order, e.g. a shopping cart of items and a shipping address.
  2. See the section on initialization. Use Factory to create an instance of IClient if you hadn't done so yet, and set the meta data that you've collected about the client of the customer.
  3. Create GetPaymentProductsParams queryParams and request a list of relevant payment products. See the relevant section of the full API reference for more details.
  4. Show the relevant payment products to the customer such that they can select one.
  5. The customer selects one of the available the payment products.
  6. Once the customer has decided which payment product should be used, you request the fields of this payment product. See the relevant section of the full API reference for more details.
  7. Based on the information retrieved in the previous step, you render a form that the customer can use to enter all relevant information for the selected payment product.
  8. The customer submits the form.
  9. Create a CreatePaymentRequest body, populate its Order and other properties depending on the selected payment product, and submit it. See the relevant section of the full API reference for more details. Do not store the information provided by the customer. The paymentProductId can be used to determine whether this payment involves a redirect to a third party. For this flow, we assume that we're dealing with a payment that doesn't require a redirect.
  10. The create payment SDK call returns a CreatePaymentResponse response. The status of the payment is accessible via response.Payment.Status. Depending on the payment product chosen and the status of the payment you can "deliver the goods" immediately, or set up a regular poll of the created payment to wait for the status. Such a poll is done using the SDK call client.Merchant("merchantId").Payments().Get(paymentId), where paymentId is response.Payment.Id. For details on the various payment products and their statuses, see Payment Products.

The high-level flow of a payment performed from pages on your server is a little different if a redirect is involved. We only describe the steps that differ from the flow without a redirect.

  1. We assume that we're dealing with a payment that involves a redirect. As mentioned above, this can be determined using the paymentProductId. Create a CreatePaymentRequest body and populate at least its Order. Additionally, populate its RedirectPaymentMethodSpecificInput by providing at least the desired ReturnUrl. The ReturnUrl defines the location to which the customer should be redirected after completing the payment process. See the relevant section of the full API reference for more details.
  2. The create payment SDK call returns a CreatePaymentResponse response. For payments involving a redirect, response.MerchantAction.RedirectData.RedirectURL defines the URL to which the customer should be redirected to complete the payment. You need to store the value of response.MerchantAction.RedirectData.RETURNMAC because it should be compared with the RETURNMAC returned by the third party at a later stage. Additionally, you need to store the value of response.Payment.Id. This paymentId is needed to check the status of the payment after the redirect.
  3. Redirect the customer to the RedirectUrl.
  4. After the payment process is completed, your customer is redirected to the ReturnUrl specified previously. In the flow shown in the figure above we assume that this URL brings the customer back to your server.
  5. Retrieve the RETURNMAC provided by the third party from the ReturnUrl. You can use the RETURNMAC to identify the customer by comparing it with the one stored previously, and to validate that the customer was redirected to you by our systems.
  6. Use the paymentId stored previously to check the status of the payment. See the relevant section of the full API reference for more details. The retrieve payment SDK call returns a PaymentResponse response. The status of the payment is accessible via response.Payment.Status. Use this status to handle the order appropriately, as described above.

Idempotent requests

To execute a request as an idempotent request, you can call the same method as for a non-idempotent request, but with an extra CallContext argument with its IdempotenceKey property set. This will make sure the SDK will send an X-GCS-Idempotence-Key header with the idempotence key as its value.

If a subsequent request is sent with the same idempotence key, the response will contain an X-GCS-Idempotence-Request-Timestamp header, and the SDK will set the IdempotenceRequestTimestamp property of the CallContext argument. If the first request has not finished yet, the RESTful Server API will return a 409 status code. If this occurs, the SDK will throw an IdempotenceException with the original idempotence key and the idempotence request timestamp.
For example:

SDK: .NET
CallContext context = new CallContext().WithIdempotenceKey(idempotenceKey);
try
{
    CreatePaymentResponse response = client.WithNewMerchant(merchantId).Payments().CreatePayment(request, context);
}
catch (IdempotenceException e)
{
    // A request with the same idempotenceKey is still in progress, try again after a short pause
    // e.IdempotenceRequestTimestamp contains the value of the
    // X-GCS-Idempotence-Request-Timestamp header
}
finally
{
    long? idempotenceRequestTimestamp = context.IdempotenceRequestTimestamp;
    // idempotenceRequestTimestamp contains the value of the
    // X-GCS-Idempotence-Request-Timestamp header
    // if idempotenceRequestTimestamp is not null this was not the first request
}
If an idempotence key is sent for a call that does not support idempotence, the RESTful Server API will ignore the key and treat the request as a first request.

Exceptions

Payment exceptions

If a payment attempt is declined by the RESTful Server API, a DeclinedPaymentException is thrown. This exception contains a reference to the payment result which can be inspected to find the reason why the payment attempt was declined. This payment result can also be used to later retrieve the payment attempt again.
For example:

SDK: .NET
try
{
    CreatePaymentResponse response = client.WithNewMerchant(merchantId).Payments().CreatePayment(request);
}
catch (DeclinedPaymentException e)
{
    Payment payment = e.CreatePaymentResponse.Payment;
    string paymentId = payment.Id;
    string paymentStatus = payment.Status;
    System.Console.WriteLine("Payment {0} was declined with status {1}", paymentId, paymentStatus);
}

Unlike direct payments, indirect payments like iDeal and PayPal usually will not cause a DeclinedPaymentException to be thrown, but instead will result in a CreatePaymentResponse return value. To determine if the payment was successfully finished, declined or cancelled, you would need to retrieve the payment status and examine its contents, especially the status field. It is recommended to use shared code for handling errors.
For example:

SDK: .NET
string paymentId;
try
{
    CreatePaymentResponse response = client.WithNewMerchant(merchantId).Payments().CreatePayment(request);
    paymentId = response.Payment.Id;
}
catch (DeclinedPaymentException e)
{
    Payment payment = e.CreatePaymentResponse.Payment;
    HandlePaymentError(payment);
    return;
}
// other code
PaymentResponse payment = client.WithNewMerchant(merchantId).Payments().GetPayment(paymentId);
if (IsNotSuccessful(payment))
{
    HandlePaymentError(payment);
}

Refund exceptions

If a refund attempt is declined by the RESTful Server API, a DeclinedRefundException is thrown. This exception contains a reference to the refund result which can be inspected to find the reason why the refund was declined. This refund result can also be used to later retrieve the refund attempt again.
For example:

SDK: .NET
try
{
    RefundResponse response = client.WithNewMerchant(merchantId).Payments().RefundPayment(paymentId, request);
}
catch (DeclinedRefundException e)
{
    RefundResult refund = e.RefundResult;
    string refundId = refund.Id;
    string refundStatus = refund.Status;
    System.Console.WriteLine("Refund {0} was declined with status {1}", refundId, refundStatus);
}

Other exceptions

Besides the above exceptions, all calls can throw one of the following runtime exceptions:

  • A ValidationException if the request was not correct and couldn't be processed (HTTP status code 400)
  • An AuthorizationException if the request was not allowed (HTTP status code 403)
  • An IdempotenceException if an idempotent request caused a conflict (HTTP status code 409)
  • A ReferenceException if an object was attempted to be referenced that doesn't exist or has been removed, or there was a conflict (HTTP status code 404, 409 or 410)
  • A DirectException if something went wrong on the Ingenico Direct platform. The Ingenico Direct platform was unable to process a message from a downstream partner/acquirer, or the service that you're trying to reach is temporary unavailable (HTTP status code 500, 502 or 503)
  • An ApiException if the RESTful Server API returned any other error

A payment attempt can now be handled as follows:

SDK: .NET
try
{
    CreatePaymentResponse response = client.WithNewMerchant(merchantId).Payments().CreatePayment(request);
}
catch (DeclinedPaymentException e)
{
    Payment payment = e.CreatePaymentResponse.Payment;
    string paymentId = payment.Id;
    string paymentStatus = payment.Status;
    System.Console.WriteLine("Payment {0} was declined with status {1}", paymentId, paymentStatus);
}
catch (ValidationException e)
{
    System.Console.Out.WriteLine("Input validation error:");
    for (ApiError error : e.Errors)
    {
        if (error.PropertyName == null)
        {
            System.Console.WriteLine("- {0}: {1}", error.Code, error.Message);
        }
        else
        {
            System.Console.WriteLine("- {0}: {1}: {2}", error.PropertyName, error.Code, error.Message);
        }
    }
}
catch (AuthorizationException e)
{
    System.Console.Out.WriteLine("Authorization error:");
    for (APIError error : e.Errors)
    {
        System.Console.WriteLine("- {0}: {1}", error.Code, error.Message);
    }
}
catch (ReferenceException e)
{
    System.Console.Out.WriteLine("Incorrect object reference:");
    for (APIError error : e.Errors)
    {
        System.Console.WriteLine("- {0}: {1}", error.Code, error.Message);
    }
}
catch (DirectException e)
{
    System.Console.Out.WriteLine("Error occurred at Ingenico Direct or a downstream partner/acquirer:");
    for (APIError error : e.Errors)
    {
        System.Console.WriteLine("- {0}: {1}", error.Code, error.Message);
    }
}
catch (ApiException e)
{
    System.Console.Out.WriteLine("Ingenico Direct error:");
    for (APIError error : e.Errors)
    {
        System.Console.WriteLine("- {0}: {1}", error.Code, error.Message);
    }
}

Exception overview

The following table is a summary that shows when each of these exceptions will be thrown:

HTTP status code Meaning Description Exception Type
200 Successful Your request was processed correctly N/A
201 Created Your request was processed correctly and a new resource was created.
The URI of this created resource is returned in the Location header of the response.
N/A
204 No Content Your request was processed correctly N/A
various; CreatePaymentResult is present in the response Payment Rejected Your request was rejected either by the Ingenico Direct platform or one of our downstream partners/acquirers. DeclinedPaymentException
various; RefundResult is present in the response Refund Rejected Your request was rejected either by the Ingenico Direct platform or one of our downstream partners/acquirers. DeclinedRefundException
400 Bad Request Your request is not correct and can't be processed. Please correct the mistake and try again. ValidationException
403 Not Authorized You're trying to do something that is not allowed or that you're not authorized to do. AuthorizationException
404 Not Found The object you were trying to access could not be found on the server. ReferenceException
409 Conflict Your idempotent request resulted in a conflict. The first request has not finished yet. IdempotenceException
409 Conflict Your request resulted in a conflict. Either you submitted a duplicate request or you're trying to create something with a duplicate key. ReferenceException
410 Gone The object that you are trying to reach has been removed. ReferenceException
500 Internal Server Error Something went wrong on the Ingenico Direct platform. DirectException
502 Bad Gateway The Ingenico Direct platform was unable to process a message from a downstream partner/acquirer. DirectException
503 Service Unavailable The service that you're trying to reach is temporary unavailable.
Please try again later.
DirectException
other Unexpected error An unexpected error has occurred ApiException

Logging

The .NET SDK supports logging of requests, responses and exceptions of the API communication.

In order to start using the logging feature, an implementation of the ICommunicatorLogger interface should be provided. The SDK provides two example implementations for logging to System.Console (SystemConsoleCommunicatorLogger) and logging to a NLog logger (NLogCommunicatorLogger).

Logging can be enabled by calling the EnableLogging method on a Client object, and providing the logger as an argument. The logger can subsequently be disabled by calling the DisableLogging method.

When logged messages contain sensitive data, this data is obfuscated.

The following code exemplifies the use of adding a logger:

SDK: .NET
IClient client = Factory.CreateClient("apiKeyId", "secretApiKey");

CommunicatorLogger logger = new NLogLogger(Logger.GetCurrentClassLogger(), Level.Info);
client.EnableLogging(logger);
//... Do some calls
client.DisableLogging();

Advanced use: Connection pooling

An IClient created using the Factory class with an IDictionary or CommunicatorConfiguration object will use its own connection pool. If multiple clients should share a single connection pool, the Factory class should be used to first create a shared ICommunicator, then to create IClient instances that use that ICommunicator:

SDK: .NET
ICommunicator communicator = Factory.CreateCommunicator("apiKeyId", "secretApiKey");
// create one or more clients using the shared communicator
IClient client = Factory.CreateClient(communicator);

Instead of closing these IClient instances, you should instead close the ICommunicator when it is no longer needed. This will close all IClient instances that use the ICommunicator instance.

If instead one of the IClient instances is closed, the ICommunicator will be closed as well. As a result, all other IClient instances that use the ICommunicator will also be closed. Attempting to use a closed IClient or ICommunicator will result in an error.

Just like IClient, ICommunicator implements System.IDisposable, and can therefore also be used in using statements.

Connection management

Just like IClient, ICommunicator also has method CloseExpiredConnections that can be used to evict expired HTTP connections. You can call this method on the ICommunicator instead of on any of the IClient instances. The effect will be the same.

Advanced use: Customization of the communication

An IClient uses an ICommunicator to communicate with the RESTful Server API. An ICommunicator contains all the logic to transform a request object to a HTTP request and a HTTP response to a response object. If needed, you can extend this class. To instantiate an IClient that uses your own implementation of ICommunicator you can use the following code snippet:

SDK: .NET
ICommunicator communicator = new YourCommunicator();
IClient client = Factory.CreateClient(communicator);

However, for most customizations you do not have to extend ICommunicator. The functionality of the default Communicator is built on on classes AuthenticaterConnectionMarshaller and MetaDataProvider, the implementation of which can easily be extended or replaced. Marshaller is used to marshal and unmarshal request and response objects to and from JSON. It is unlikely that you will want to change this module. The other modules are needed to communicate with the Ingenico Direct platform:

  • The RESTful Server API endpoint URI.
  • A Connection, which represents one or more HTTP connections to the Ingenico Direct server.
  • An Authenticator, which is used to sign your requests.
  • A MetaDataProvider, which constructs the header with meta data of your server that is sent in requests for BI and fraud prevention purposes.

For your convenience, a CommunicatorBuilder is provided to easily replace one or more of these modules. For example, to instantiate an IClient that uses your own implementation of Connection, you can use the following code snippet:

SDK: .NET
Connection connection = new YourConnection();
ICommunicator communicator = Factory.CreateCommunicatorBuilder(dictionary, "apiKeyId", "secretApiKey")
    .WithConnection(connection)
    .Build();
Client client = Factory.CreateClient(communicator);

Logging

To facilitate implementing logging in a custom Connection, the SDK provides utility classes RequestLogMessageBuilder and ResponseLogMessageBuilder. These can be used to easily construct request and response messages. For instance:

SDK: .NET
// In the below code, logger is the CommunicatorLogger set using enableLogging.
// Note that it may be null if enableLogging is not called.
string requestId = Guid.NewGuid().ToString();
RequestLogMessageBuilder requestLogMessageBuilder =
    new RequestLogMessageBuilder(requestId, method, uri);
// add request headers to requestLogMessageBuilder
// if present, set the request body on requestLogMessageBuilder
logger.Log(requestLogMessageBuilder.Message);
// send the request
int statusCode = ...;
ResponseLogMessageBuilder responseLogMessageBuilder =
    new ResponseLogMessageBuilder(requestId, statusCode);
// add response headers to responseLogMessageBuilder
// if present, set the response body on responseLogMessageBuilder
logger.Log(responseLogMessageBuilder.Message);