Testing
Test Environment
Base URL: https://api-test.sweuze.com/v1
The test environment connects to provider sandboxes - no actual charges occur.
Payment Method Testing
- MBWay (
mbway-eupago): use any Portuguese-format test phone number (e.g.+351912345678); simulate the approval in the Eupago sandbox app. - Multibanco (
multibanco-eupago): returns testentity/referencepairs. Simulate payment via the Eupago sandbox. - Neteller (
neteller-paysafe): use Paysafe sandbox wallet credentials. - Paysafecard (
paysafecard-trustpayments): use TrustPayments sandbox test vouchers. - Card (
card-rillpay): use Rillpay sandbox test cards at the hosted checkout (covers 3DS, declines, soft-declines). Remember to includecustomerType,kycStatusonpaymentMethod, andemail,phone,firstName,lastName,dateOfBirthoncustomer. - Open Banking (
openbanking-rillpay): use Rillpay sandbox banks at the hosted checkout. IncludecustomerType,kycStatusonpaymentMethod, andemail,firstName,lastName,dateOfBirth,nationalityoncustomer(nophonerequired).
Pre-Production Checklist
- Payment intents can be created for every method enabled on your merchant account (check
GET /payment-methods?currency=EUR) - Customer redirects work correctly (Rillpay, Neteller, Paysafecard)
- Requisites are displayed correctly (MBWay, Multibanco)
- Return URLs handle all statuses
- Webhooks are received and signature-validated
- Orders are fulfilled only on
payment_intent.succeeded/payment.succeeded- never on return URLs - Error scenarios handled gracefully (
422,502) - Idempotency prevents duplicates (same
referencereuses the existing intent) - Monitoring configured
Going Live
- Configure merchant account in production environment
- Create API keys in production portal
- Update base URL to production
- Configure webhook endpoints and secrets
- Verify webhook accessibility from production
- Enable monitoring and alerting