Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.augustus.com/llms.txt

Use this file to discover all available pages before exploring further.

Test your Open Banking integration in Sandbox first, then in Production before going live.

​
Sandbox testing

You can test your Augustus integration using sandbox banks with fake login data and the built-in Sandbox Tools. This lets you simulate every flow (success, failure, refunds, and more) before going live.

​
1. Test checkout flows with sandbox banks

Create a checkout session in sandbox and visit the redirect URL to see available sandbox banks. Follow the instructions below with the provided credentials to test a range of flow types.
BankCountryCurrencySchemesCredentialsInstructions
Test Bank marketAnyAnySEPA Credit, SEPA InstantUsername: random
Password: random
OTP: random		For success enter any OTP
For failure enter OTP = 666
Deutsche Bank SandboxDEEURSEPA Credit, SEPA InstantIBAN: DE17215730140403340300
Account Holder Name: random
Branch: 615
Account: 4033403		1€ for success
100€ for failure
KD Bank SandboxDEEURSEPA Credit, SEPA InstantIBAN: DE39499999600000005111
Account Holder Name: random
Customer ID: VRK1234567890ALL
password: password
SCA method: Mobile
SCA code: 123456		For success select any SCA method and use the SCA code 123456 if it asks for one
Natwest SandboxGBGBPFaster PaymentsUsername: 123456789012
Password: displayed on screen
BBVA SandboxESEURSEPA Credit, SEPA InstantIBAN: ES2501822200160201933547
username: user1
password: 1234
SCA code: 123456		To trigger failure click “Cancel” → “Aceptar” in bank UI
Alior SandboxPLEURElixir, SEPA Creditusername: 60370698
password: 12345678		Approve payment in bank interface - simulates delayed bank update
PKO BP SandboxPLEURElixir, SEPA Creditn/aUse buttons in the bank UI to set the desired outcome:
Sukces → Success

​
2. Simulate successful payins with Sandbox Tools

When Test Mode is activated, you get access to Sandbox Tools in the dashboard to simulate successful payins and refunds.
1

Create an order via API

The order will be in the processing status.
2

Open the order in the dashboard

Find your payment in the Orders table and click it for the detailed view.
3

Simulate funding

The status updates to paid with a corresponding webhook.
Sandbox tools for simulating order flows
These simulations don’t work if you have direct settlement enabled.

​
3. Simulate incoming transactions manually

  • Turn on test mode.
  • In the Deposits tab, press Create deposit.
  • Simulate a fiat manual bank transfer or USDC deposit with any amount.
Useful for testing unreferenced or unexpected incoming payments.
If you don’t have the Deposits feature enabled, this triggers an automatic return. Speak to your account manager to configure it.

​
Production testing

Once you’ve tested in sandbox, switch to production. Toggle off test mode in the Dashboard and use your live API keys.
Production testing involves real money. Always start with small amounts and verify your integration thoroughly before processing larger payments.
Test caseDescriptionExpected outcome
Successful payments from multiple banksTest payments from 4+ banks with different amountsPayments succeed and webhooks are received
User cancels the flowCancel the payment flow during bank authentication for 2+ banksPayments fail with the appropriate failure reason
Insufficient fundsAttempt a payment from an account with insufficient fundsPayment fails with the insufficient_funds failure reason
Test each scenario with small amounts and verify that your webhook endpoints receive the correct status updates.

​
What’s next