How merchants get started
01
Tell us about your business — sector, markets, volumes
02
We issue your API credentials and a test environment
03
Integrate with two API calls and go live
One product, one integration
One integration and one API, for customers paying from a wallet they control.
SpendLayer Direct
Your customer chooses SpendLayer Direct at your checkout and authorises on the SpendLayer consent screen, using the 16-digit code tied to their wallet. That creates a mandate between them and you, with a defined amount, frequency and limit. Funds move on-chain, straight to your own wallet.
Recurring, natively
Subscriptions and instalments collect without the customer re-authorising each time — the capability no other alternative payment method in this space offers.
Auditable end to end
Every authorisation and collection is a public on-chain event, verifiable without access to our systems.
How
Direct
works at checkout
The authorisation code is an access credential. Your customer enters it on the SpendLayer consent screen, never on your checkout, and it never passes through your systems. It lets them authorise a mandate without handling their private key.
Customer authorises on the SpendLayer consent screen with their 16-digit code
A mandate is created — amount, frequency, duration, ceiling
Collections run on schedule — your customer never re-authorises, and you sign each one
Funds move on-chain and the transfer is final
Monthly
Subscription
-12.50 USDC
Recurring
Top-up
-9.99 USDC
Instalment
Plan
-29.00 USDC
Why on-chain matters to you
Flows your partners can verify for themselves, rather than taking anyone’s word for them
Independently auditable
Acquirers and partners can verify flows on-chain, not by asking us for a report.
Compliance in code
Limits and restrictions are encoded and deterministic, not back-office policy.
Final transfers
Transfers are final on-chain. No dispute path, and no clawback months later.
Customers cards miss
Reaches wallet-native customers you cannot serve through a card checkout.
Two calls and a signature
Create a payment request from your server, send the customer to the hosted consent screen we return, and release the order when the completion webhook arrives. Authentication is an API key plus an HMAC-SHA256 signature over the request body.
Distributors welcome
Merchants can integrate SpendLayer Direct themselves, and many prefer not to. If you already serve merchants in these sectors — as a payment service provider, an integrator, a platform or an agency — you can introduce them to SpendLayer under a partner agreement, and we will support the merchants you bring.
Frequently asked questions
Still have questions?
Tell us about your business and we will get you set up with credentials and a test environment.
Yes. SpendLayer Direct can be integrated straight into your own checkout. The whole integration is two API calls — one to create a payment request and return a checkout link, one to follow its status — with webhooks if you would rather not poll.
Tell us about your business and we will issue API credentials and a test environment. The full reference is published at spendlayerapm.com/docs.
Every SpendLayer wallet is linked to a unique 16-digit authorisation code. Your customer uses it to authorise a mandate without having to handle their private key, which is what lets SpendLayer Direct work as an alternative payment method at checkout.
Your customer chooses SpendLayer Direct at your checkout and is sent to the SpendLayer consent screen, where they enter the code and approve the mandate — the agreed amount, frequency and limits. The code is an access credential, so it is entered only on that screen and never on yours, and it never reaches your systems. It does not expose their private key. It is what creates the mandate they approve, and funds move only under that mandate.
Collection stops from that point. Revocation is unilateral and takes effect on-chain, so you will not be able to collect further instalments under that mandate, and there is no retry path.
In practice this behaves like a cancelled direct debit: you keep everything already collected, and you handle the cancellation in your own billing logic. Every revocation is an on-chain event, so it is visible to your systems immediately rather than surfacing later as a failed charge.
Yes. Your signing key is generated in your own browser the first time you sign in. It never reaches SpendLayer, is never stored on our systems, and we cannot recover, reset or restore it.
Back it up before you go live. If you lose it you lose the ability to sign collections from your wallet, and nobody can restore it for you.
Yes. You can originate and submit any collection a mandate permits yourself, without SpendLayer preparing anything. Our scheduling is a convenience, not a dependency.
The full merchant integration reference is published at spendlayerapm.com/docs — endpoints, request signing, the status lifecycle and webhook payloads, with worked Node.js examples.
It covers the hosted consent flow. Recurring collection under a mandate is handled separately, so raise it with your integration contact if you need it.
Availability varies by product and jurisdiction, and sanctioned jurisdictions are excluded throughout. Tell us where you operate and we will confirm what is available to you.
