gc-fis-zelle application.
The following table lists the two charts deployed for FIS Zelle.
Both charts mount the shared
fis-zelle SOPS secret. For setup steps, see Get started.
Configuration properties
Configure each chart in its values file underruntimes/<runtime>/values/gc-fis-zelle/.
Values to obtain from FIS
Obtain the following values from FIS and set them in the values files. These values are environment-specific, so they have no default.gc-fis-zelle-payment-order-connector
Set the following properties inpayment-order-v2.values.yaml. Defaults reflect the ecos-dev installation; confirm production values with the Grand Central team.
gc-fis-zelle-party-authentication-connector
Set the following properties inparty-authentication-v0.values.yaml.
SOPS secrets
Both charts read credentials and mTLS material from thefis-zelle SOPS secret (existingSecretName: fis-zelle). On ecos-dev the secret lives in the gc-fis-zelle namespace.
The following table lists keys stored in that secret.
Supported operations
For the operation-to-endpoint tables, see Overview. For the full contract, see the API playground.Events
Bothgc-fis-zelle-payment-order-connector and gc-fis-zelle-party-authentication-connector are synchronous and do not publish or consume events.
Error mapping
The connector maps vendor error codes to Grand Central status codes. For the full list, see Error codes.Dependencies
- FIS Zelle Small Business REST API (outbound), reachable at
zelle.rest.base.url - FIS PeoplePay SOAP endpoint (outbound), reachable at
zelle.soap.endpoint - FIS OAuth2 token endpoint (outbound), for Bearer token authentication
fis-zelle-connector-sdk(shared HTTP and SOAP configuration for FIS Zelle)