-
Notifications
You must be signed in to change notification settings - Fork 67
Extensions concept
The payment gateway supports "extensions" in versions 1.6 and higher. Extensions will help you retrieve additional parameters that might be interesting for your use-cases, but would rather bother other merchants. Extensions are independent and you can use multiple extensions at the same moment in time. Please contact [email protected] for activation of particular extensions.
Technically speaking, extensions are more flexible than changes to the core API structure because extensions do not impact the cryptographic signing of core API operations. Each extension has its own signature, i.e. the gateway validates merchants' requests and so should the merchant validate the responses.
Extensions are not specific API operations. Extensions are integrated into the existing API operation in a transparent way, with their own signatures (as briefly characterised above). Please refer to the specs of individual extensions for more technical information, as well as actual examples.
Exact date and time of transaction authorization
- Payment lifecycle
- Integration and API security
- Activation of the production environment
- Test cards and credentials
- API Sunset
- Payment Authentication
- Basic Payment
- OneClick Payment
- Custom Payment
- Apple Pay
- Google Pay
- Collecting partial card payment
- ČSOB Payment Button
- Payment Skip Pay
- API Integration
- Request Signing and Response Signature Validation
- API Methods Overview
- Basic Methods
- Methods for OneClick Payment
- Methods for Apple Pay
- Methods for Google Pay
- Methods for ČSOB Payment Button
- Methods for Skip Pay
- Purchase metadata