In private build
One integration.
Every payment provider.
Spacenine sits between your checkout and your payment providers. Connect each provider once, decide where every payment goes, and see exactly what happened to it.
Set up once. Then every payment follows the route.
Connect each provider once
Add your provider accounts with guided steps for every credential. Each connection shows what it can take, whether it is working, and what depends on it.
- Several accounts at one provider, told apart by a label
- Test and Live credentials kept apart
- A warning before a key expires
In your provider's dashboard, open Developers, then API keys. Create a key and paste it here.
Create an account for each store, brand or market
Every account has its own API keys and its own payment methods. Switch a method on, choose the connection it goes to, and the account is ready.
- A Test side and a Live side from the start
- Copy a tested setup from Test to Live
- Start a new account as a copy of another
Send a payment with one request
The same request works for every payment method and every provider behind it. Spacenine picks the route, talks to the provider, and answers with one result.
- A Test key as soon as the account exists
- One answer, with every attempt listed
- Nothing provider-specific in your code
curl https://api.spacenine.io/v1/payments \ -H "Authorization: Bearer sk_test_..." \ -d amount=5000 \ -d currency=EUR \ -d payment_method=card
{
"id": "pay_8Hq2",
"status": "succeeded",
"amount": 5000,
"currency": "EUR",
"transactions": [
{ "connection": "Stripe", "status": "declined" },
{ "connection": "Adyen", "status": "approved" }
]
}Add rules when you need them
Draw the path of a payment as steps on a canvas: a condition, a first choice, a backup, a split. Try it with a sample payment, then publish.
- Route by payment method, country or amount
- A backup when a payment is declined or a provider does not answer
- Share traffic between providers
Read what happened to any payment
Each payment keeps one numbered history: which rule chose the provider, what the provider answered, and everything after, down to the last refund.
- Every step in order, with what caused it
- The same story for support and for developers
- Rows are only added, never changed
- 1Payment created, 50.00 EURYour API call
- 2Rule "Card routing" chose StripeWorkflow
- 3Declined by the card's bank. It can be retried.Provider answer
- 4Backup chosen: AdyenWorkflow
- 5ApprovedProvider answer
- 6Captured, 50.00 EURProvider answer
- 7Refund, 10.00 EURA teammate, in the dashboard
Spacenine is being built now.
Leave your email and we will write to you when early access opens.