Skip to main content
Follow the steps in Get started with connectors before proceeding. FIS Zelle access: An active FIS Zelle arrangement (retail, small business, or both) and sandbox or production access through FIS CodeConnect. Network connectivity: Network connectivity between Banking OS and FIS Zelle. For supported options, see Network connectivity. Environment details: You need the following environment details from FIS:
The FIS user acceptance testing pack usually includes sandbox gateway URLs and non-secret identifiers. Share application secrets and the bank secret key with your Backbase support team through a secure channel.

Prepare the connector

Backbase deploys this connector. To share connectivity details and provide the environment details, follow these steps:
  1. Share connectivity details. Share connectivity details between Banking OS and FIS Zelle as described in Network connectivity.
  2. Send environment details to Backbase. Send the environment details in the table above to your Backbase support team.
  3. Set the line of business on each call. 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 Banking OS 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.
For property names and defaults, see Reference.

Test your integration

When you call the unified API, include your Banking OS subscription key in the request header. The following table shows the required header: Suggested smoke checks in sandbox:
  1. 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.
  2. Payer account management: Register a funding account (include routing number), list accounts, then retrieve one by ID.
  3. 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.
Cause: FIS credentials, application identifiers, or the bank secret key are missing, expired, or wrong for the environment.Solution: Confirm the values with FIS, ask your Backbase support team to update the connection, and retry in the same environment (for example, UAT only with UAT credentials).
Cause: Banking OS cannot reach the FIS gateway or retail SOAP endpoint in time.Solution: Confirm network routing and that the FIS environment is up.
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.
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.
Cause: Sign-in prerequisites failed (secret key, return URL, session context, or wrong line of business).Solution: Verify the return URL and secret key for small business, confirm the customer is already enrolled, and confirm the call uses a channel that supports the sign-in operation.
Cause: Request volume exceeded the rate limit for the Banking OS subscription.Solution: Reduce request volume or ask the Banking OS team to adjust the APIM rate limit for the program.