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.

Your checkoutOne payment, 50.00 EUR SpacenineRule: card paymentsFirst choice, then a backup SStripeDeclined, can be retriedfirst choice AAdyenApprovedbackup CCheckout.comNot needed this time
Your checkoutOne payment, 50.00 EUR
SpacenineRule: card payments. First choice, then a backup.
S
StripeDeclined, can be retried
A
AdyenApproved
C
Checkout.comNot needed this time
The customer saw one checkout. You can read every step.

Set up once. Then every payment follows the route.

1

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
2

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
3

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
RequestPreview. The API may change before launch.
curl https://api.spacenine.io/v1/payments \
  -H "Authorization: Bearer sk_test_..." \
  -d amount=5000 \
  -d currency=EUR \
  -d payment_method=card
Response
{
  "id": "pay_8Hq2",
  "status": "succeeded",
  "amount": 5000,
  "currency": "EUR",
  "transactions": [
    { "connection": "Stripe", "status": "declined" },
    { "connection": "Adyen",  "status": "approved" }
  ]
}
4

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
5

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

Spacenine is being built now.

Leave your email and we will write to you when early access opens.