Native API Integration
Introduction:
In this integration method, all front-end pages must be developed by the merchant, allowing users to complete payments entirely within the merchant’s interface.
Supports both onramp and offramp scenarios:
- For onramp, the ACH response provides a link that directly redirects to the payment gateway page.
- For offramp, the ACH response provides the receiving wallet address of the order.
- Require PCI certificate(Payment Card Industry Data Security Standard, PCI DSS) to integrate.
Before integrating with this mode, please contact us to evaluate whether it is suitable for your use case.
Domains:
Test: https://openapi-test.alchemypay.org
Prod: https://openapi.alchemypay.org
API Endpoints
API Call Recommendations
- First, call the
Crypto QueryAPI to check the supported crypto and limits. - Then, call the
Fiat QueryAPI to check the available payment methods and limits. - If an estimate is needed, call the
Quote QueryAPI. - Call the
Get TokenAPI to retrieve the user token. - Call the
Payment Method Form QueryAPI to retrieve the form information required for the payment method. - Call the
Submit FormAPI to submit the user’s payment account information.(Google Pay and Apple Pay don't need to call this interface.) - Call the
Create OrderAPI.
Support Payment
Onramp ONLY support payment below
| Payment | payWayCode | Fiat |
|---|---|---|
| Visa/ Master Card | 10001 | Check on supported fiat |
| Google Pay | 701 | Check on supported fiat |
| Apple Pay | 501 | Check on supported fiat |
| Neteller | 52004 | EUR |
| Skrill | 52005 | EUR |
| QRIS | 10004 | IDR |
| Virtual Account | 10003 | IDR |
| PayID | 3002 | AUD (Require user KYC level2) |
| Bank Transfer | 3001 | AUD (Require user KYC level2) |
Updated 1 day ago