Development
Getting started with self-made integrations
Table of contents
Subpages
- Errors, problem solving and corner cases
- General: Integration development
- PHP and development libraries
- API Types
- Create part payment widget
- Rounding
- Recognized metadata
- Payment providers in simplified flow
- Permissions and passwords – Platform access
[!IMPORTANT] Important about staging versus production If you are planning to develop or install plugins, you must run both a test and a production environment. This allows you to verify functionality in a controlled setting before release. Ensure your test and production environments are identical to minimize differences in behavior. Note: Our PHP libraries no longer support PHP 5–7. All integrations should use PHP 8 or later. The current standard requirement for ECom and related libraries is PHP 8.1 or higher. However, as PHP 8.1 is gradually becoming deprecated—meaning it only receives limited security updates and will soon lose active support from frameworks and community—future requirements may shift to newer PHP versions.
Downloadables
We host logos and images for our markdown documents within our Bitbucket repositories.
Source code and support
We use Bitbucket for public source code hosting. Our previous JIRA instance has been deprecated and is no longer in active use. While some historical records remain accessible, it will eventually be discontinued. An internal issue management platform has replaced it.
You can find our public repositories here: https://bitbucket.org/resursbankplugins/?visibility=public
Callback handling
With the introduction of MAPI, callback handling has been redesigned. Rapid callback issues that could previously cause race conditions are no longer expected.
Instead of registering a generic callback URL for all requests, MAPI now registers specific callbacks per purchase during each transaction. This ensures safer, more predictable, and event-specific communication between systems.