Skip to main content
This guide takes you from identity to the status tracking of a first SoleasPay transaction.

1. Prepare your domains

All protected business requests go through the gateway.
All OAuth2/OIDC requests go through Mysoleas Identity Cloud.
Store these URLs in environment variables. This makes tests, workers, and back-office tools easier to maintain.

2. Get a JWT

If you integrate the Sign in with Mysoleas button, use authorization_code with PKCE. If your backend acts on its own behalf, use client_credentials.
The response contains an access_token. This token is the JWT you send to the gateway.

3. Call the gateway

Send the token in x-sp-auth-token.
You can also send context headers when your application manages several environments or countries.

4. Choose a service

List available services before you create a transaction. The service code becomes the provider value in payment payloads.
A service that can be used for a collection must have is_active: true and is_can_collect: true. A service that can be used for a disbursement must have is_active: true and is_can_disburse: true.

5. Launch a collection

The standard flow uses three calls: intent, execute, then status.
In the request, customer_wallet must not include the country calling code.
The response contains transaction_reference. Use this value to execute and track the transaction.

6. Track the status

Poll the status until you get a final state.
Final states are COMPLETED, SUCCESS, FAILED, CANCELLED, and REFUNDED.