Settlement timing
Do not estimate a pay-in’s completion time from its payment method alone. Bank cutoffs, non-business days, provider processing, and required customer actions can all affect timing. Swipelux does not publish one fixed SLA for every pay-in capability. Confirm any contractual timing requirement with Swipelux for the customer’s enabled capability and operating countries.Choose an available capability
Retrieve the customer’s capabilities and select one that supports the intended pay-in. Use the returned capabilitydata.id as the capabilityId when you create a quote.
Do not hard-code a list of payment methods. Swipelux can add methods over time, and availability can differ by customer.
See capabilities and tasks for the readiness flow. Then follow receive funds to create and execute the quote.
Track the transfer
After execution, readGET /v3/transfers/{transferId}. Treat the latest data.state as the source of truth.
Inspect data.stateDetail and data.openTaskIds when a transfer needs attention. Subscribe to webhooks and keep the status synchronized until the transfer reaches an outcome your product handles.
Do not mark a transfer complete from an expected schedule. Show customers the current transfer state instead.