Version 2.3.0

This release includes the following enhancements:

• the dLocal card source for use in LATAM https://docs.checkout.com/docs/request-a-payment-using-dlocal
• the Files client https://docs.checkout.com/docs/disputes
• the Disputes client https://docs.checkout.com/docs/disputes

Version 2.2.0

This release includes the following enhancements:

• PaymentRecipient was updated for Account Funding Transaction compatibility

Version 2.1.0

This release includes the following enhancements:

• PaymentRequest can now have the Processing object specified

Version 2.0.0

This release includes the following enhancements:

• amount is no longer of type int; instead it is of type long

This release contains breaking changes.

Version 1.3.0

This release includes the following enhancements:

• Include acquirer processing details (processing) in payment responses and payment actions. For more details see the API Reference.

Version 1.2.1

This release includes the following enhancements:

• HttpResponse is disposed immediately after use in ApiClient

Version 1.2.0

This release includes the following enhancements:

• AlternativePaymentSource and AlternativePaymentSourceResponse now support complex alternative payment source objects. You can use the AsAlternativePayment() extension method on a payment response source to access alternative payment specific data.
• Added support for the Sources API enabling the creation of reusable payment sources such as SEPA direct debits that can later be used to request payments. Further information can be found in our docs.

Version 1.1.0

This release includes the following enhancements:

• Added an Approved property to payment actions returned by IPaymentsClient.GetActionsAsync. This indicates whether a specific action was successful avoiding the need for any logic around response codes.
• When retrieving a payment with IPaymentsClient.GetDetailsAsync using a session ID, the response now includes an array of action summaries that contain the original response code/summary for an action. The most common reason for this is to determine the decline reason for an Authorization for redirect payment methods such as 3-D Secure. A GetAuthorizationAction convenience method is provided for this use case. Further details can be found on the Wiki.

You can download this release from Nuget

Version 1.0.0

This release contains breaking changes

• Adds mapping of the approved field on Get Payment responses. Similar to the approved field returned when a payment is initially requested, this new field allows you to easily determine whether an existing payment was successfully authorized or captured without requiring any logic around the Checkout.com response code.
• Renamed Cancelled payment status to Canceled. Since we used Americanized english in all of our API products, this updates the SDK to that convention. This change will only impact merchants using Alternative Payment methods that support cancellation.
• Changed all enumerations returned in API responses to string constants. This was done to avoid any code breakages caused by the introduction of new enum values (e.g. Payment statuses) for developers that have not yet updated the SDK and will be our convention moving forward for any response string enumerations. With the exception of the Canceled rename above, the member names have remained the same as the existing enum types, so unless you have explicitly referenced these types, it should not break your code.

You can upgrade to the latest version using NuGet.

Version 0.3.0

• New sample application demonstrating card payments including 3-D Secure!
• Support for alternative payments via the AlternativePaymentSource:

            var alternativePaymentSource = new AlternativePaymentSource("giropay") 
            {
                { "bic", "TESTDETT421" }, 
                { "purpose", "CKO giropay" }
            };