Documentation
Set up a merchant project, collect payments, and reconcile provider confirmations.
The app supports hosted checkout, reviewed API withdrawals, signed postbacks, and status reconciliation. Provider testing requires a genuine A-Pay test project.
1. Obtain your project
Contact A-Pay through your client support chat for an assigned API domain, test project ID, API key, access key, signing key, and approved methods. Each merchant uses separate credentials.
2. Configure the merchant
In Administration → Merchants, open the merchant’s Dedicated A-Pay project. Enter credentials, select approved methods, and save disabled. The server operator must approve the assigned hostname in APAY_ALLOWED_HOSTS. Verify the read-only connection, then enable the test project. Keys remain encrypted and hidden.
3. Register postback URLs
Give A-Pay support the public HTTPS endpoints shown below. These URLs also appear in the merchant’s integration settings and admin project page.
POST https://vabnapay.com/api/apay/postback/deposit
POST https://vabnapay.com/api/apay/postback/withdrawalLocalhost cannot receive external postbacks. Deploy with a public HTTPS APP_URL before testing delivery.
4. Collect a payment
In the merchant portal, create a deposit using A-Pay processing and an approved method. Open the checkout link and continue to A-Pay’s hosted payment page. The Laravel backend creates the provider request; API keys stay on the server.
5. Confirm the outcome
The app verifies callback signatures and transaction ownership before updating the ledger. Duplicate final confirmations are handled without applying funds twice. A return-page query parameter never credits a payment.
6. Test withdrawals and reconciliation
Add a recipient, then request a funded A-Pay withdrawal. Administrators review and submit it once. Provider callbacks or authenticated status checks confirm the result. Uncertain submissions remain reserved for reconciliation.
The server operator should run Laravel’s scheduler for expiry and reconciliation. Settlements and provider refunds use the documented operator review and external-confirmation workflow.
7. Complete provider acceptance
Ask A-Pay support for test callbacks covering successful and failed outcomes. Check amounts, methods, duplicate callbacks, limits, and balances before switching to live credentials.
Official provider references
A-Pay start integration · Hosted payment page · Postback specification
Connect your own website
Merchants can create revocable, environment-specific API keys under Settings → Website API. Use the server API to create payment links, read outcomes, and check balances. Configure signed webhook deliveries to notify your store of final outcomes. The authenticated settings page includes request examples and signature-verification instructions.
Wallet accounts and fees
Administration → Merchants → select merchant includes Wallet accounts and Fees & commissions. Import receiving wallets from CSV, disable unused destinations, and define future deposit, withdrawal, or settlement charges. Merchant statements show snapshotted platform fees separately from provider charges.