> For the complete documentation index, see [llms.txt](https://developer.emporix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.emporix.io/release-notes/archive/2023/2023-07-11-ce-payments.md).

# 2023-07-11: CE - Payment Gateway Service

### Overview

The new Payment Gateway Service provides a flexible architecture and the efficiency and security for your payment processes. With the integration of [Spreedly](https://www.spreedly.com/), we are empowering you with a robust, and scalable payment orchestration solution that simplifies the complexities of managing multiple payment gateways, processors, and methods.

On top of it, you can define an additional payment gateway in parallel to Spreedly in case your customer has a contract with a different provider. If you are running multiple sites on Emporix, you can offer different payment methods and currencies on each of them.

Together with Spreedly, we ensure your customers' payment data is secure. The solution is fully compliant with Level 1 PCI, and GDPR requirements in different geographies, worldwide.

### New features

| Features                                | Benefits                                                                                                                                                                                                                                 |
| --------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Configuration of payment strategies** | Simplify the integration & speed up the implementation of Spreedly payment gateways by just configuring a new payment strategy within Spreedly for a new payment method - no coding.                                                     |
| **Payment configuration per site**      | Merchant employees can just configure the relevant payment method on site level by using the .                                                                                                                                           |
| **Transaction log**                     | Have a transparent overview within the about the transaction history for every order.                                                                                                                                                    |
| **Refund creation**                     | The merchant customer service can trigger refunds from the without logging in to several payment provider backoffices.                                                                                                                   |
| **Capture**                             | Provides the flexibility to adapt the capture trigger based on your business, for example: digital products you might want to capture instantly. In other cases, you might need to reserve an amount and capture the final amount later. |

### Fixes and improvements

None as these are new services.

### Known problems

No known problems at time of release.

### Documentation and links

* [User Business Scenarios](/user-guides/customer-use-cases/scenarios-introduction/payment-process.md)
* [System Management - Payments Configuration Guides](/user-guides/extensibility-and-integrations/payments.md)
* [Payment Gateway API](/api-documentation/api-guides/checkout/payment-gateway.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.emporix.io/release-notes/archive/2023/2023-07-11-ce-payments.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.