> ## Documentation Index
> Fetch the complete documentation index at: https://docs.byzly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Payment facilitators

> Process card payments as a payment facilitator (PayFac) by sending sub-merchant details to supported payment services.

A payment facilitator (PayFac), also called an aggregator, processes payments for its sub-merchants under its own account with an acquirer. In each authorization, a PayFac identifies both itself and the sub-merchant the payment is for. This lets the acquirer attribute funds, reporting, and the buyer's statement descriptor to the right sub-merchant.

Gr4vy supports the PayFac model on selected card connectors. On those connectors, Gr4vy sends the PayFac and sub-merchant details that the payment service expects with each transaction.

## How it works

PayFac support is enabled per connection, by request only. It isn't available by default. Contact Gr4vy to have it configured on a connection.

* **Sub-merchant details are set on the connection.** You don't pass them per transaction. Each PayFac connection carries the details of one sub-merchant, so set up a connection for each sub-merchant you process for.
* **Your payment service account must allow it.** The payment service must enable PayFac processing on your account before it accepts sub-merchant details. Gr4vy can't enable this for you.

## Supported connectors

| Connector | Details |
| - | - |
| [Fiserv IPG - Card](/connections/payments/fiserv-card#payment-facilitator-omnipay) | Uses Fiserv's Omnipay platform. Sends the sub-merchant's merchant category code (MCC), legal name, email, merchant ID, and address. |
| [Cybersource - Card](/connections/payments/cybersource-card#payment-facilitators) | Sends your aggregator ID for the card scheme, your PayFac name, and the sub-merchant's ID, name, email, address, phone number, and MCC. Also sets a merchant descriptor that combines your PayFac name with the sub-merchant's details. |

Other connectors don't have built-in PayFac support. Some accept sub-merchant fields per transaction through connection options instead. For example, the Adyen connector passes its `additionalData` connection option through to Adyen. Check the connector's page and the [new transaction](/reference/transactions/new-transaction) reference for the connection options each connector supports.

## Request support on another connector

Gr4vy adds PayFac support to connectors on request. Before you ask, check with the payment service that it supports the PayFac model for your account, and in the countries you need. Payment services differ in whether they offer it and in which fields they require, and Gr4vy can't confirm this on their behalf.

Once the payment service confirms its support and the fields it needs, contact Gr4vy to discuss adding them to the connector.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.