Fintoc Business Accounts

QuotaGuard gives a customer-controlled Fintoc Business Accounts API client two stable public IPv4 sources. Add both subscription addresses to Fintoc's optional IP Restrictions control so approved outbound requests can continue through either load-balanced route while off-list sources are rejected. QuotaGuard has provided static-IP proxy service since 2013.

• Business Accounts scope: The route covers requests sent from the customer's application through QuotaGuard to the Fintoc Business Accounts API.
• Dashboard configuration: Fintoc documents IP Restrictions under API Keys and accepts individual IP addresses or CIDR blocks. Add both QuotaGuard addresses before activation because Fintoc warns that enabling the control with no address rejects every request.
• Separate Fintoc controls: API keys, JWS request signing, nonce and timestamp handling, and idempotency remain in place. A stable network source does not replace them.
• Shield-first transport: QuotaGuard Shield is recommended when transfer requests carry sensitive banking and recipient data. It encrypts the customer-to-proxy hop while preserving the application's HTTPS session to Fintoc without decrypting its payload.
• Static remains valid: QuotaGuard Static can satisfy the source-IP restriction and preserves the application's HTTPS session, but it does not add Shield's TLS encryption around the customer-to-proxy hop.
• Outbound path only: Fintoc webhooks travel from Fintoc to the customer's HTTPS endpoint. Outbound QuotaGuard routing does not replace webhook receipt, signature verification, source verification, retry, or idempotency controls.

Product boundary: QuotaGuard provides stable network sources and transport choices. QuotaGuard, Fintoc, and IP Restrictions do not make a financial workflow compliant by themselves.