A little clarity. A better next step.

Acru connects payment acceptance, payouts, platform operations, and risk workflows. The right configuration depends on your business model, markets, methods, and how funds need to move.

Offer Apple Pay, Google Pay, PayPal, and Venmo; local and bank payments such as Pix, SEPA, and ACH; and buy now, pay later options including Klarna and Afterpay. Cards and crypto are also part of the payment mix. Your approved method mix is confirmed during onboarding and varies by market and use case.

Payouts move available funds to an eligible recipient or destination. Settlement determines when and how processed funds become available to your business. Acru scopes both around your program, including timing, reserves, and eligible rails.

Yes. Choose a hosted experience, embedded components, or an API-led approach based on the control your product needs. The team will help map the integration and the payment states your application needs to handle.

Acru’s platform workflows connect merchant onboarding, buyer payments, allocation of proceeds, and seller payouts. Your team gets merchant-level context across transaction activity, balances, and risk.

Not yet. Authorization approves a payment, capture submits it for collection, and settlement determines when the proceeds become available under your agreement. Your available balance may also reflect fees, refunds, disputes, or reserves.

Check the original payment’s verified outcome before requesting another payment. A browser timeout does not prove a charge failed. Keep the order reference and payment state connected so your team can resolve the attempt without charging twice.

A refund returns funds through the merchant’s payment process. A dispute is raised through the customer’s bank or payment provider. If a dispute is already open, check its state before issuing a refund to avoid reimbursing the same payment twice.

Compare the full cost of your payment mix: method and network charges, cross-border and conversion costs, refunds, disputes, payouts, and any minimum or platform fees. Review settlement schedules and reserve terms separately because they affect cash availability.

Possibly, but portability must be confirmed with the current and receiving providers. Review token compatibility, consent, and secure transfer requirements before setting a migration date. Do not export raw card details through ordinary files or email.

Confirm a written implementation scope that names your approved methods, markets, currencies, integrations, and funding terms. It should distinguish available capabilities from planned work and identify the tests and approvals needed before production.

Start with a conversation about your business, expected volume, markets, and current payment flow. Acru will identify the relevant program requirements, commercial structure, and integration path.