Payment orchestration for dating and social

What goes wrong without orchestration

• The one acquirer that took the app terminates it when the chargeback ratio crosses a threshold, and every subscriber must enter a card again at the next one.
• Renewals are charged without a reminder or a one-click cancellation, and each forgotten renewal becomes a dispute instead of a refund.
• A dispute arrives with a card number and a date, and matching it to the account, subscription and login history takes a day.

What orchestration changes

Routing by BIN and country across several acquirers and cascading of a declined payment to the next; recurring charges by token, Apple Pay and Google Pay for the first payment; limits per card, account and terminal, and a rolling reserve where the acquirer requires one; refunds through the acquirer that took the payment before a dispute opens; the chargeback ratio visible per acquirer in the journal; every payment, renewal, refund and chargeback journaled for five years and traceable to the account. The app’s PSP enables the methods from the catalogue; the licensed acquirer settles the funds and decides what it takes.

Subscriptions and credits

• Subscriptions: the first payment with 3-D Secure where the acquirer requires it; renewals by token as merchant-initiated charges; an expired card is marked before the renewal.
• Credits and gifts: one-off card or wallet payments with limits per card and account against card testing.
• Crypto: USDT for markets where card acquirers do not take the vertical.