By supporting a range of alternative payment solutions, Solidgate empowers businesses to expand their reach and boost customer satisfaction across diverse markets.
The features for managing payments with APMs include payment initiation, subscription automation, refund processing, and real-time transaction tracking.
Init payment
Via API Init payment APIOperation for initiating a payment using an alternative payment method performs order creation and prepares the transaction for payment, allowing the customer to proceed with the payment process.
Init future payment
Via API Use the Host-to-Host or Payment Form flow to initiate a future payment.| one-time | 1-click | recurring | unscheduled | |
|---|---|---|---|---|
| Alipay alipay | supported | not supported | not supported | supported |
| Bizum bizum | supported | not supported | not supported | not supported |
| Cash App cashapp | supported | not supported | not supported | not supported |
| MB WAY mbway | supported | supported | supported | not supported |
| WeChat wechatpay | supported | not supported | not supported | supported |
future_usage object Use this flow to define intent for subsequent use of the customer's payment credentials, token-based future charges.
It ensures compliance with scheme rules, reduces declines on future payments, and improves success rates. future_usage object Required
Description
Defines the usage of stored payment credentials.
Should be provided either future_usage or product_id for payment_method
alipay
,
bizum
,
mbway
,
wechatpay
.
Example
{
"future_usage": {
"payment_type": "recurring"
}
}
payment_type
string
Required
Description
Type of the token usage scenario.
- one-time no token created, for one-off use
- 1-click token for future CIT without re-entering details
- recurring token for fixed scheduled MIT, for subscriptions
- unscheduled token for unscheduled/variable MIT, for auto-top-up
paymentIntent future_usage object Use this flow to define intent for subsequent use of the customer's payment credentials, token-based future charges.
It follows the same rules as the API init payment request, reducing declines and improving success rates. future_usage object Required
Description
Defines the usage of stored payment credentials.
Should be provided either future_usage or product_id for payment_method
bizum
,
cashapp
.
Example
{
"future_usage": {
"payment_type": "one-time"
}
}
payment_type
string
Required
Description
Type of the token usage scenario.
- one-time no token created, for one-off use
To streamline integration for merchants using product services, the system automatically calculates the appropriate payment intent by combining payment_type and product_id.
When both are provided, the system ensures no conflict between them. In the case of a conflict, such as a
one-time
payment with a
recurring
product, the request is declined. If only the product_id is provided, the payment_type is determined based on the product type.
Future usage |
Product type by |
Validation result |
Calculated value |
|---|---|---|---|
| - | - | DECLINED | - |
| - | one-time | OK | one-time |
| - | recurring | OK | recurring |
| one-time | - | OK | one-time |
| one-time | one-time | OK | one-time |
| one-time | recurring | DECLINED | - |
| 1-click | - | OK | 1-click |
| 1-click | one-time | OK | 1-click |
| 1-click | recurring | DECLINED | - |
| recurring | - | OK | recurring |
| recurring | one-time | DECLINED | - |
| recurring | recurring | OK | recurring |
| unscheduled | - | OK | unscheduled |
| unscheduled | one-time | OK | unscheduled |
| unscheduled | recurring | OK | unscheduled |
Recurring
Via API Recurring APIFor alternative payment methods Alipay, WeChat Pay, GCash, PayPal, Mercado Pago, Pix or UPI, a token-based recurring payment refers to an automatic charge applied to a customer's payment method at predetermined intervals.
After the first successful payment, you can leverage the token system for recurring transactions. The token containing essential payment method information is accessible via the
order token field from: With this token, initiate a recurring request using token with payment_method
alipay
,
wechatpay
,
gcash
,
mbway
,
paypal-vault
,
mercadopago
,
pix
or
upi
.
For payment_method
alipay
,
wechatpay
, the token must be obtained from a previous successful transaction with future_usage payment_type set to
unscheduled
.
For payment_method
mbway
, the token must be obtained from a previous successful transaction with future_usage payment_type set to
1-click
.
Refund
Via API Refund APM order APISolidgate handles refunds for both card payments and APMs through its secure payment gateway integration.
The APM refund request supports alternative payment methods, including PayPal, Pay by Bank, and others, allowing to initiate refunds for successfully processed orders.
It is vital to be aware that refunds in APMs, particularly in cash-based methods, may be limited or unavailable. PayPal does not provide an ARN for refunds. It is recommended to generate a Refund confirmation via Hub for orders. Via Hub To issue a refund
- Go to Payments > Orders.
- Select the needed order to go to the order details page.
- In the top-right corner, click on the Refund button.
- In the appeared form, complete the refund information:
- Select Full refund or Partial refund
- Specify the refund reason
- Click on Refund to confirm.
Once the refund is successful , you can get the Refund confirmation on the Transactions section and share it with the customer. The refund confirmation serves as proof of a completed refund transaction and can be used for several purposes:
- Share it with the customer as proof that the refund has been processed successfully, building trust and transparency in your business relationships.
- Update your financial records to ensure accurate bookkeeping for tax purposes, track refund patterns, and maintain a clear financial history.
- Present it to financial institutions if they have any inquiries about the transaction.
If a chargeback is opened, the refund option is inactive in both the Hub and the bank’s system to prevent duplicate payouts.
Refunds can be declined primarily because the cardholder’s account cannot accept them. The common reasons for a declined PayPal refund include:
- Connection timed out: PayPal did not respond while processing the return. Please repeat the refund at a later time.
- Channel to dispute the refund:
- For
dispute_channelinternal make a refund through the Hub. - For
dispute_channelexternal , the refund cannot be processed at this stage and can only be disputed. However, it can be successful if the bank reversal is confirmed in the PayPal admin panel.
- For
Check status
Via API Check status APIRequest for receiving current order status.
The key benefit is that it allows merchants to efficiently monitor and manage their payments. It provides comprehensive information about the order's status, payment method, transaction details, and customer information.