Set up your test account
Everything in this documentation is built and verified against Straumur's test environment (also called staging). Nothing you do there moves money, and the endpoint URLs shown on every page point at it. Live is a separate system with its own hostnames and credentials; you switch to it only when you go live.
Getting access
Email developers@straumur.is. You will get:
- a test agreement with the e-commerce solutions you asked for (Hosted Checkout, Payment Gateway, Payment Links, …) enabled,
- a login to the test Merchant Portal, or the test Partner Portal if you integrate on behalf of several merchants.
From the portal you create your API key and copy the Terminal Identifier for each solution you use; see Contracts and Terminals.
Test hostnames
| Test | |
|---|---|
| Checkout API (all endpoints in these docs) | https://checkout-api.staging.straumur.is/api/v1/… |
| Hosted payment page (where shoppers are redirected) | https://hosted-checkout.staging.straumur.is |
| Merchant Portal | merchant.staging.straumur.is |
| Partner Portal | partner.staging.straumur.is |
You never build the hosted payment page URL yourself; the url in the create-checkout response already points at it. The row is here for integrators who allow-list redirect targets.
For Components, set the environment option to "test".
Paying in test
Use the test cards — real cards are not accepted in the test environment. The same page explains how to simulate declines and how to test Apple Pay and Google Pay.
Receiving webhooks in test
Register your endpoint in the test portal and take the HMAC key from there. Test webhooks are delivered exactly like live ones, including retries, so a test integration exercises the same code path. See Webhook configuration and Delivery and retries.