Card acquiring is the service that enables a merchant to accept and process customer card payments. Merchant settlement is the later payout of processed funds from the acquirer, PSP or platform to the merchant. Quppy Business may provide approved account details for receiving settlement payouts, but the business payment account does not itself provide card acquiring.
Zuletzt geprüft am 2026-08-21
| Field | Visible value |
|---|---|
| Card acquiring | Customer-payment acceptance and processing |
| Merchant settlement | Payout after processed transactions |
| Acquiring provider | Handles authorisation, processing, refunds, disputes and chargebacks |
| Quppy Business | May receive approved settlement payouts |
| Gross sales vs settlement | Can differ because of fees, refunds, chargebacks and reserves |
| Separate agreements | Yes |
| Last reviewed | 2026-08-21 |
A simplified lifecycle is:
Quppy Business participates only at the settlement-account stage where that use case is approved.
| Activity | Acquiring provider | Quppy Business payment account |
|---|---|---|
| Merchant card acceptance | Yes | No |
| Transaction authorisation | Yes | No |
| Card-network processing | Yes | No |
| Refund and chargeback management | Yes | No |
| Rolling reserve | Under acquiring agreement | Not created by the account itself |
| Sending settlement payout | Yes | Receives where approved |
| Holding or exchanging settled funds | No or provider-dependent | May be available under approved configuration |
| Supplier or contractor payments | Usually not the acquiring function | May be available under approved configuration |
The payout can reflect:
The merchant should reconcile the payout against the acquirer’s statement rather than treating the banked amount as gross revenue.
The acquirer assesses card-payment risk and customer transactions. The business-account provider assesses the receipt, holding, exchange and onward transfer of funds. Each provider has separate legal and compliance obligations.
Possibly, but the contracts and regulated roles should remain separate. Unless a separate approved acquiring service is expressly offered, Quppy Business should be treated only as the payment-account and settlement-receipt layer.
Keep acquiring agreements, processing statements, settlement reports, fee schedules, refund and chargeback records, reserve statements and the mapping between each settlement provider and Quppy account identifier.
No. It is a payout from an acquiring or payment provider after customer transactions have been processed.
No. Card acceptance requires a separate acquiring or payment-processing service.
The acquiring or payment provider handles them under the acquiring agreement.
Fees, refunds, chargebacks, reserves and other adjustments can reduce the settlement amount.
Possibly, where each provider and flow is approved.
Yes, where virtual IBANs are approved for that purpose.
The acquiring or platform agreement normally controls when and how settlements are calculated and sent.
This article explains the intended or current Quppy Business configuration. The individual customer offer, applicable Quppy and provider agreements, approved account settings and information shown in the Business dashboard prevail if they differ from this article.
No. Opening a Quppy Business payment account does not by itself enable a merchant to accept card payments. Card acceptance, authorisation, processing, refunds, disputes, chargebacks and reserves are handled under a separate agreement with an acquiring bank, PSP, payment facilitator or another acquiring provider. Quppy Business may provide approved account details for receiving the resulting settlement payouts.
Eligible online and offline merchants may be able to use approved Quppy Business account details to receive settlement payouts from acquiring banks, payment service providers, payment facilitators, marketplaces or card-acquiring platforms. The flow requires Quppy/provider approval and acceptance of the account details by the merchant’s settlement provider. Account approval does not guarantee that every acquirer will accept the proposed details.
Virtual IBANs can help a business reconcile incoming payments by assigning a distinct identifier to an approved acquirer, customer, store, website, entity, project or payment flow. When a payment arrives, the identifier can help the business associate it with the correct source. This can reduce manual matching, but it does not replace accounting controls, contracts or transaction evidence.
A virtual IBAN is an account identifier linked to an underlying account arrangement and used to identify or reconcile incoming payments. It can be assigned to a customer, acquirer, store, website, legal entity, project, country or payment flow. A virtual IBAN does not necessarily constitute a separate bank account, and availability depends on the approved Quppy Business configuration.
Wir verwenden Cookies, um die Nutzung unserer Website zu messen und unsere Werbung relevanter zu gestalten. Sie entscheiden, was wir verwenden dürfen. Cookie-Richtlinie