Pay-ins and pay-outs describe opposite directions in a business payment flow. A pay-in collects money from a payer; a pay-out sends money to a destination. Write each requirement separately before selecting a provider.
Map the participants and direction
Record the payer, recipient, business purpose, currency and destination. Separate the collection requirement from what happens later. A wallet appearing on a collection list does not establish that it is available as a payout destination.
Keep conversion separate
Changing currency is another step, not a synonym for collection or payout. Ask when a rate is quoted, what fees are displayed and what conditions apply to confirmation. Do not assume a rate or timing from a general product description.
Confirm the enabled account scope
Published methods are a starting point for discussion. Confirm which methods and destinations apply to the merchant account, along with eligibility, fees and limits. Do not treat a marketing list as an automatic account entitlement.
Agree result handling
Business, engineering and operations should agree which evidence confirms the payment outcome, when fulfilment can proceed and who handles unresolved transactions. Ask for the applicable integration documentation before choosing implementation details.
Test the agreed workflow
Record expected and observed results for the scenarios the sandbox can demonstrate. Keep environment limitations visible. A test result is not proof of production settlement timing or future availability.
CVPay scope
CVPay supports VND, PHP and USDT collections and payouts with one merchant account and one API. Pay-in categories include bank transfers, QR and wallets. Listed Vietnam methods are VietQR, MoMo, ZaloPay and Viettel Money; Philippine methods are GCash, Maya, GrabPay and QR Ph. Enabled methods must be confirmed per account. Payouts can reach local bank accounts in Vietnam and the Philippines, or USDT wallets; this does not establish wallet payouts for the named pay-in methods.
For fiat/USDT conversion, rates and fees are shown before confirmation and the confirmed rate applies within the quote's validity period. Payment-status notifications carry signatures. KYB review is required; a sandbox precedes production and the environments are separate.