Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.

Skip to main content

Accepting online payments

Merchants can accept online payments with Swan.

Merchant profile

Before accepting online payments, each merchant needs a merchant profile.

Online payment methods​

Your merchants can request the following online payment methods to accept payments with Swan:

Credit transfers

You can also accept payments to a Swan account with credit transfers.

Payment links redirect customers to a Swan-hosted payment page where a customer can choose from the merchant's eligible enabled payment methods. These optimized payment pages are customizable with the merchant's name, logo, and accent color.

Your merchants can create links to share with their customers by email or text message. They could also include a QR code on an invoice, scannable by the customer with their mobile device.

→ Learn how to create payment links to accept card payments.

Merchant payments​

Merchant payments include one or more transactions. For example, one payment might include both a capture and refund transaction.

These transactions are grouped together in the merchant payment object. Swan recommends using the merchant payment object in your integration to help merchants match orders, invoices, and sales to the correct object. This provides better traceability and can help reconcile issues more efficiently.

Payment object statuses​

The merchant payment object has distinct statuses to follow a payment's lifecycle. All payments begin in the Initiated status. From Initiated, a payment may be directly Captured, Canceled by the merchant, or Rejected by Swan or another participant in the payment scheme, such as the customer's payment service provider. For card payments, the flow may proceed from Initiated to Authorized before being either Captured or Canceled. After capture, a payment may still be Refunded by the merchant or Disputed by the customer, depending on the payment method.

Final status
Funds received
Rejected
Canceled
Refunded
Disputed
Captured
Merchant
payment initiated
Initiated
Authorized
Only applies to card payments
Payment Object StatusExplanation
InitiatedThe payment object has been created, but the payment is not yet authorized or guaranteed.
AuthorizedApplies only to card payments. The payment has been authorized by the customer's bank. The funds are guaranteed but not yet captured.
CanceledThe payment was canceled. Funds can no longer be captured. This is a final status.
RejectedThe payment was rejected by Swan or another participant in the payment scheme before the funds were captured. This is a final status.
CapturedThe payment is successfully authorized (for card payments) or processed (for all other payment methods), and the funds are debited from the customer's account. This can be the final status of a successful payment flow, unless the customer disputes the payment or requests a refund.
RefundedThe payment was reversed by the merchant either for the full amount or partially depending on the payment method. This is a final status.
DisputedThe customer disputed the payment with their bank either for the full amount or partially depending on the payment method. This is a final status.

Payment object balances​

The merchant payment object has distinct balances to follow a payment's lifecycle.

Payment object balanceExplanation
totalAuthorizedThe total authorized amount for this merchant payment.
availableToCancelThe authorized amount that can be released. Refer to this balance to verify whether the payment can be canceled. Cancellations must be done before the amount is captured, or earlier in the payment's lifecycle for some payment methods.
totalCanceledThe total amount canceled for this merchant payment.
availableToCaptureThe amount available for merchants to capture if the capture isn't automatic.
totalCapturedThe amount captured by the merchant. For card payments with automatic capture, totalCaptured is always equal to totalAuthorized.
availableToRefundThe amount the merchant can refund. Use this balance to know if a payment is eligible for a refund.
totalRefundedThe total amount refunded for this merchant payment.
totalDisputedThe total amount of this merchant payment disputed by the customer.