Encrypted connections
GIBP uses secure HTTPS connections so information is protected while travelling between your device and our services.
GIBP is designed to protect customer information, restrict access to sensitive systems and require verified provider updates wherever a live regulated payment service is enabled.
GIBP uses secure HTTPS connections so information is protected while travelling between your device and our services.
Account access is authenticated and customer records are isolated so your recipients, payment information and history are not exposed to other users.
Sensitive service credentials are kept away from the customer-facing website and restricted to protected systems.
Where live payments are enabled, provider updates must be verified before they can change payment state.
Application changes pass automated code-quality, type-safety and production-build checks before release, reducing the risk of unsafe changes reaching customers.
Where a provider requires identity, beneficiary, sanctions or transaction checks, those requirements belong in the relevant service journey.
GIBP combines secure account access, encrypted communications, restricted system access, isolated customer records and carefully controlled connections to payment services so that sensitive information is exposed only where it is needed.
Only authenticated users and authorised systems should be able to reach protected customer information.
Your recipients, payments and transaction history are kept within your account rather than shared across users.
When provider webhooks are enabled, their authenticity must be checked before they can change payment state.
Code changes are automatically validated before deployment and production errors are monitored after release.
If you suspect unauthorised access, an unexpected payment or a security issue, contact GIBP through Help straight away. Never share your password, one-time verification code or full banking credentials in response to an unsolicited message.