What does a provider need to supply before an integration can start?
A reachable sandbox and current API documentation. Integration speed depends on both, since mappings, fallback handling and certification are tested against the provider's environment. When something blocks, NORBr's payment team works directly with its contacts at the provider rather than leaving the operator to chase the answer.
In detail
A reachable sandbox and current API documentation. Integration speed depends on both, since mappings, fallback handling and certification are tested against the provider's environment. When something blocks, NORBr's payment team works directly with its contacts at the provider rather than leaving the operator to chase the answer.
Two things
A reachable sandbox and current API documentation. The sandbox is where mappings, error handling, fallback behavior and settlement file parsing are tested; without it, the integration cannot be certified. The documentation has to match the sandbox, which is not always the case, and should cover authorization, capture, refund, void, dispute events, settlement files and the provider's decline codes.
What slows integrations
- Sandboxes that are unstable, incomplete or behave differently from production.
- Documentation that is outdated or missing the settlement file format.
- Certification processes that require the provider's team to schedule test sessions.
- Decline codes that are not documented, so the mapping is built from observation.
How blockers are handled
NORBr's payment team works directly with its contacts at the provider rather than leaving the operator to chase answers. Providers that are used to integrating with platforms usually respond in days. The operator's part is the commercial agreement and its own onboarding with the provider, which can run in parallel. Operators who want a specific provider connected should introduce NORBr to their contact there early, since the provider's responsiveness is the main variable in the timeline.