Get started

Complete the following prerequisites and configuration to start using the FIS Zelle Connector.

Prerequisites

Before you begin, make sure you meet the following requirements:

You have completed the steps in Get started with connectors.
You have an active FIS Zelle arrangement (retail, small business, or both) and sandbox or production access through FIS CodeConnect.
You have network connectivity between Grand Central and FIS Zelle. For supported options, see Network connectivity.
You have the environment details in the following table from FIS:

Parameter	Description
FIS API gateway base URL	Base URL for small-business REST calls (`zelle.rest.base.url`)
Retail SOAP endpoint URL	Endpoint for retail Zelle SOAP calls (`zelle.soap.endpoint`)
Frontend, source, and environment identifiers	Values FIS expects on each request (`zelle.fis.fe-id`, `zelle.fis.source-id`, `zelle.fis.environment-id`)
Application identifier	Application identity for FIS (`zelle.fis.application-id`)
OAuth2 client credentials	Client ID and client secret for the FIS token endpoint
Bank secret key (small business)	Secret used in the Zelle sign-in request and related FIS identity configuration
Retail SOAP mTLS material	Client PKCS12 keystore, passphrase, and CA certificate for PeoplePay

The FIS user acceptance testing (UAT) pack usually includes sandbox gateway URLs and non-secret identifiers. Share application secrets and the bank secret key only through a secure channel with Grand Central research and development or Grand Central operations.

Configuration

To configure the connector, follow these steps:

Complete any Grand Central APIM or subscription-key setup your environment requires. For the shared connector setup flow, see Get started with connectors.
Obtain environment-specific values from FIS. For the property list, see Reference.

Set the connector properties in the gc-applications-live repository. On ecos-dev, the Argo CD application gc-fis-zelle deploys two charts that share the fis-zelle SOPS secret: The following table lists the charts and values files.

Chart	Values file	Domain
`gc-fis-zelle-payment-order-connector`	`payment-order-v2.values.yaml`	Payer and payer account management
`gc-fis-zelle-party-authentication-connector`	`party-authentication-v0.values.yaml`	Zelle sign-in

The following example shows a typical file location:

├── iPaaS
└── azure/runtimes
    └── <runtime>
        └── values
            └── gc-fis-zelle
                ├── payment-order-v2.values.yaml
                └── party-authentication-v0.values.yaml

<runtime> is usually dev, test, and so on.

Store credentials and certificates in the fis-zelle SOPS secret. Do not put passwords, secret keys, or PKCS12 material in plain values files. For more information, see Configure a connector. Example shape for payment-order values (replace placeholders with values from FIS and the Grand Central team):

connector:
  existingSecretName: fis-zelle
  properties:
    retail.endpointType: soap
    business.endpointType: rest
    zelle.rest.base.url: "https://api-gw-uat.fisglobal.com"
    zelle.soap.endpoint: "<retail-soap-endpoint>"
    zelle.fis.application-id: "<application-id>"
    zelle.fis.source-id: "<source-id>"
    zelle.fis.fe-id: "<fe-id>"
    zelle.fis.environment-id: "uat"
    # OAuth2 client-id/secret, PKCS12 passphrase, and zelle.fis.secret-key
    # belong in the fis-zelle SOPS secret, not in plain text
  traits:
    knativeservice:
      minScale: 0
    logging:
      level: INFO

Include the Line-Of-Business header on unified API calls (Retail or Business). The connector routes to the matching FIS channel.

FIS requires a bank routing number when you register a funding account. When the Grand Central request has no routing-number field, pass the ABA routing number in the customFields.bankCode field on that request. When FIS requires the bank name for Retail SOAP, also pass the customFields.bankName field on that request.

Test your integration

When you call the unified API, include your Grand Central subscription key in the request header. The following table shows the required header:

Key	Value
`api-key`	`<your_subscription_key>`

Suggested smoke checks in sandbox:

Payer management: Register a test customer, then search. For Business, you can also retrieve by ID. For Retail, use search instead of retrieve by ID.
Payer account management: Register a funding account (include routing number), list accounts, then retrieve one by ID.
Sign in to Zelle: Initiate sign-in and confirm a usable Zelle URL or redirect payload.

For the full contract, see API playground. For operations and properties, see Overview and Reference.

Troubleshooting

If the connector does not respond as expected, check these common scenarios.

Authentication failure with FIS

Cause: FIS credentials, application identifiers, or the bank secret key are missing, expired, or wrong for the environment.Solution: Confirm the values with FIS, update the fis-zelle SOPS secret with the Grand Central team, and retry in the same environment (for example UAT only with UAT credentials).

Timeout or connectivity error

Cause: Grand Central cannot reach the FIS gateway or retail SOAP endpoint in time.Solution: Confirm network routing and that the FIS environment is up. If both look healthy, contact GC Support.

Payer registration rejected

Cause: Required customer fields for that channel are missing (small business often needs identifiers such as user ID, date of birth, tax ID, and terms acceptance date).Solution: Compare the request with the API playground contract for the operation, supply the missing values for that line of business, and retry.

Funding account rejected

Cause: The bank routing number or the account details in the request aren’t in the format FIS expects.Solution: Include the ABA routing number in the customFields.bankCode field on the request. When FIS requires the bank name for Retail SOAP, add the customFields.bankName field on the request. Verify the account number and account type, and confirm that the payer registration ID is valid.

429: Rate limit exceeded

Cause: Request volume exceeded the rate limit for the Grand Central subscription.Solution: Reduce request volume or ask the Grand Central team to adjust the APIM rate limit for the program.

Grand Central Connectors

Release notes

Prerequisites

Configuration

Test your integration

Troubleshooting

​Prerequisites

​Configuration

​Test your integration

​Troubleshooting

Prerequisites

Configuration

Test your integration

Troubleshooting