In the following part of documentation you will find a supportive information for easy integration with SolidGate.
Code | Description |
---|---|
0.01 | General decline |
0.02 | Order expired |
0.03 | Illegal operation |
1.01 | Authentication failed |
2.01 | Invalid Data |
2.02 | Invalid amount |
2.03 | Invalid Currency |
2.05 | Order not found |
2.06 | Invalid CVV2 code |
2.07 | Request Is empty |
2.08 | Invalid card number |
2.09 | Invalid expiration date |
2.10 | Invalid 3DS flow on the merchant side |
2.11 | Invalid 3DS flow on the bank side |
2.12 | Invalid 3DS flow |
2.13 | Invalid IP |
2.14 | Subscription error |
2.15 | SCA require 3D authentication |
2.16 | Subscription is locked |
3.01 | Card is blocked |
3.02 | Insufficient funds |
3.03 | Payment amount limit excess |
3.04 | The transaction is declined by the issuer |
3.05 | Call your bank |
3.06 | Debit card not supported |
3.07 | Card brand is not supported |
3.08 | Do not honour |
3.09 | 3D-Secure authentication required |
3.10 | Suspected fraud |
4.01 | Card is in a black list |
4.02 | Stolen card |
4.03 | Restricted card |
4.04 | Lost card |
4.05 | Suspected fraud |
4.06 | Blocked by Country/IP |
4.07 | Trusted antifraud system |
4.08 | AVS mismatch |
4.09 | Solid antifraud engine |
5.01 | 3D secure verification failed |
5.02 | Invalid Card Token |
5.03 | Application error |
5.04 | Merchant is not configured correctly |
5.05 | Merchant is not activated yet |
5.06 | Duplicate order |
5.07 | exceeded API calls limits |
5.08 | Invalid transaction |
5.09 | Merchant not found |
5.10 | Processor does not support requested API method |
5.11 | Invalid routing |
6.01 | Unknown decline code |
6.02 | Connection error |
7.01 | Card token not found |
7.02 | Google payment error |
7.03 | Smart cascade decline |
7.04 | 3DS cascade to 2D |
7.05 | Apple online payment error |
7.06 | Token generation error |
Value | Description |
---|---|
created | The order was created |
processing | The order is in processing |
3ds_verify | The order goes through 3DS verification |
approved | The order is approved and the payment is successful |
declined | The order was declined |
refunded | Funds by the order were transferred back to the cardholder |
auth_ok | Funds were successfully reserved |
auth_failed | Reservation of the funds is failed |
settle_ok | Funds were successfully settled |
void_ok | Operation of fund reservation was voided |
partial_settled | Part of the funds was successfully settled |
Value | Description |
---|---|
created | The transaction was created |
fail | An error processing the transaction |
processing | The transaction is in processing |
success | Transaction successfully processed |
verify | The transaction is going through 3DS verification |
Value | Description |
---|---|
pay | Operation of funds reservation |
recurring | Operation of payment by the token |
recurring-auth | Operation of funds reservation by the token |
refund | Operation for transferring funds back to the cardholder |
resign | Operation of payment by the token + cvv |
resign-auth | Operation of hold amounts by the token + cvv |
auth | Operation of funds reservation |
settle | Operation of settling funds reservation |
void | Operation of canceling the funds reservation |
apple-pay | Apple Pay Payment |
google-pay | Google Pay Payment |
Refund reason codes are provided for both Void and Refund operations. You could use them for the analysis of the return structure or trigger specific events on your side.
Code | Description | When is used |
---|---|---|
0001 | Request by Support user | Deprecated |
0002 | Fraud - PSP | Deprecated |
0003 | Fraud - Support | Deprecated |
0004 | Fraud - SP Antifraud | Deprecated |
0005 | Fraud - MaxMind | Deprecated |
0006 | Fraud - Threatmetrix | Deprecated |
0007 | Fraud - Manual check | Deprecated |
0008 | Potential Chargeback - Retrieval Request | Deprecated |
0009 | Potential Chargeback - Refund after Chargeback | Deprecated |
0010 | System Error - Product | Deprecated |
0011 | System Error - SignedPay | Deprecated |
0012 | System Error - PSP | Deprecated |
0013 | Ethoca alert - Fraud | Deprecated |
0014 | Ethoca alert - Friendly Fraud | Deprecated |
0015 | Ethoca alert - Potential Chargeback | Deprecated |
0016 | Verifi alert - Fraud | Deprecated |
0017 | Verifi alert - Friendly Fraud | Deprecated |
0018 | Verifi alert - Potential Chargeback | Deprecated |
0019 | VMPI Alert | Deprecated |
0020 | Mismatch status (Decline - Approved) | Deprecated |
0021 | Solid - Request by User | This refund reason is used for all manual refunds via My.Solid |
0022 | Solid - Issuer Fraud Notification | When the issuer reports a fraudulent charge directly to Solid, our Team may do a refund after contacting the client. |
0023 | Solid - Risk Department | After our team detects fraud, the client may ask to refund transactions. |
0024 | Solid - Retrieval Request | If the issuer posts a Retrieval Request, the client could choose to refund the transactions. |
0025 | Solid - Prevention Alert | Refunds are automatically issued with this code when we receive a prevention alert. Previously, the following refund codes 0016,0017,0018,0019 were used. |
0026 | Solid - System Error | This code is used rarely, only in case of technical problems between Solid, providers, and payment networks. |
0027 | Solid - Antifraud | This code is used for automatic refund action in our antifraud. |
0028 | Solid - Expired Authorization | After auth expires, we will issue the void with this code. |
Disputes are the general term for actions that are performed by a user to cancel the transaction without interacting with the merchant.
Solid provides a feature of smart retrying failed subscriptions payments, which helps our merchants to recover revenue and decrease the involuntary churn rate of the customers.
After the initial collection of the invoice is failed, the retry mode would turn On, and the state of the subscription would change to "redemption".
While the subscription is in state "redemption", we would retry the invoice collection four times. The interval between the retries is based on the customer, payment method and card data features.
Moreover, we provide the option to automatically apply a Discount in % if we receive a decline "Insufficient Funds" during the last payment attempt.
You could select the predefined retry strategies in the Hub while creating or editing Subscription Product details.
The description of all available retry strategies is provided below.
Name in Hub: "#1 - Weekly 0% /0% /0% /0%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | - |
2 | On the nearest Friday | - |
3 | 2 days after the previous retry | - |
4 | 5 days after the previous retry | - |
Name in Hub: "#2 - Weekly 0% /0% /0% /25%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | - |
2 | On the nearest Friday | - |
3 | 2 days after the previous retry | - |
4 | 5 days after the previous retry | 25% |
Name in Hub: "#3 - Weekly 0% /0% /50% /0%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | - |
2 | On the nearest Friday | - |
3 | 2 days after the previous retry | 50% |
4 | 5 days after the previous retry | - |
Name in Hub: "#4 - Weekly 0% /0% /0% /75%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | - |
2 | On the nearest Friday | - |
3 | 2 days after the previous retry | - |
4 | 5 days after the previous retry | 75% |
Name in Hub: "#5 - Weekly 0% /0% /25% /50%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | - |
2 | On the nearest Friday | - |
3 | 2 days after the previous retry | 25% |
4 | 5 days after the previous retry | 50% |
Name in Hub: "#6 - Weekly 10% /25% /50% /75%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | 10% |
2 | On the nearest Friday | 25% |
3 | 2 days after the previous retry | 50% |
4 | 5 days after the previous retry | 75% |
Name in Hub: "#7 - Weekly 25% /50% /75% /75%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | 25% |
2 | On the nearest Friday | 50% |
3 | 2 days after the previous retry | 75% |
4 | 5 days after the previous retry | 75% |
Name in Hub: "#8 - Weekly 0% /15% /40% /65%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | - |
2 | On the nearest Friday | 15% |
3 | 2 days after the previous retry | 40% |
4 | 5 days after the previous retry | 65% |
Name in Hub: "#9 - Monthly 0% /0% /0% /0%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | - |
2 | On the nearest Friday | - |
3 | 9 days after the previous retry | - |
4 | 19 days after the previous retry | - |
Name in Hub: "#10 - Monthly 0% /0% /0% /25%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | - |
2 | On the nearest Friday | - |
3 | 9 days after the previous retry | - |
4 | 19 days after the previous retry | 25% |
Name in Hub: "#11 - Monthly 0% /0% /0% /50%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | - |
2 | On the nearest Friday | - |
3 | 9 days after the previous retry | - |
4 | 19 days after the previous retry | 50% |
Name in Hub: "#12 - Monthly 0% /0% /0% /75%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | - |
2 | On the nearest Friday | - |
3 | 9 days after the previous retry | - |
4 | 19 days after the previous retry | 75% |
Name in Hub: "#13 - Monthly 0% /0% /25% /50%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | - |
2 | On the nearest Friday | - |
3 | 9 days after the previous retry | 25% |
4 | 19 days after the previous retry | 50% |
Name in Hub: "#14 - Monthly 0% /25% /50% /75%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | - |
2 | On the nearest Friday | 25% |
3 | 9 days after the previous retry | 50% |
4 | 19 days after the previous retry | 75% |
Name in Hub: "#15 - Monthly 25% /50% /50% /75%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | 25% |
2 | On the nearest Friday | 50% |
3 | 9 days after the previous retry | 50% |
4 | 19 days after the previous retry | 75% |
Name in Hub: "#16 - Monthly 0% /15% /40% /65%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | - |
2 | On the nearest Friday | 15% |
3 | 9 days after the previous retry | 40% |
4 | 19 days after the previous retry | 65% |
Name in Hub: "#17 - Monthly 0% /0% /0% /30%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | - |
2 | On the nearest Friday | - |
3 | 9 days after the previous retry | - |
4 | 19 days after the previous retry | 30% |
Name in Hub: "#18 - Monthly 0% /0% /50% /0%"
# | Retry Interval | Discount |
---|---|---|
1 | 1 day after initial collection | - |
2 | On the nearest Friday | - |
3 | 9 days after the previous retry | 50% |
4 | 19 days after the previous retry | - |
№ | Test card | Result of using |
---|---|---|
1 | card_number: “4532456618142692” zip_code: 99801 | charge: success, recurring: success, refund: success |
2 | card_number: “5589800801939886” card_holder: “TRINITY SIMON” card_exp_month: “01” card_exp_year: “2029” card_cvv: “695” card_token: “card5589800801939886” card_bin: CURACAO | charge: success, recurring: success, refund: success |
3 | card_number: “6763428189229070” card_holder: “JOHN SNOW” card_exp_month: “11” card_exp_year: “2029” card_cvv: “111” card_token: “card6763428189229070" card_bin: ITALY | charge: success, recurring: success, refund: success |
4 | card_number: “4916400491851” zip_code: 99801 | charge: success recurring: fail refund: success |
5 | card_number: "4024007166621440" card_exp_month: "09" card_exp_year: "2029" card_holder: "KAITLYN BECKER" card_cvv: "137" card_token: “card4024007166621440” card_bin: UNITED KINGDOM | charge: success recurring: Decline - “Insufficient funds refund: success |
6 | card_number: “4929360879023” zip_code: 99801 | error: {code: 0.01 , message: “General decline”} |
7 | card_number: “5151948477715326” zip_code: 99801 | error: {code: 3.02, message: “Insufficient funds”} |
8 | card_number: “4532003312475364” card_holder: “BRANDON BROWN” card_exp_month: “05” card_exp_year: “2029” card_cvv: “957” card_bin: SPAIN | error: {code: 0.02, message: “Order expired”} |
9 | card_number: “4929213352238223” card_holder: “LANDON GILSON” card_exp_month: “06” card_exp_year: “2029” card_cvv: “204” card_bin: UNITED KINGDOM | error: {code: 0.03, message: “Illegal operation”} |
10 | card_number: “5462413335551193” zip_code: 99801 | error: {code: 3.01, message: “Card is blocked”} |
11 | card_number: “4485664001324176” zip_code: 99801 | error: {code: 3.03, message: “Payment amount limit excess”} |
12 | card_number: “5361250317309261” card_holder: “JESSICA DICKINSON” card_exp_month: “09” card_exp_year: “2029” card_cvv: “629” card_bin: REPUBLIC OF KOREA | error: {code: 3.04, message: “Transaction is declined by issuer”} |
13 | card_number: “4916242642369774” card_holder: “BLAKE YOUNG” card_exp_month: “04” card_exp_year: “2029” card_cvv: “595” card_bin: UNITED KINGDOM | error: {code: 3.05, message: “Call your bank”} |
14 | card_number: “5299389115628964” card_holder: “GABRIELLE WINTER” card_exp_month: “03” card_exp_year: “2029” card_cvv: “772” card_bin: RUSSIAN FEDERATION | error: {code: 2.06, message: “Invalid CVV2 code”} |
15 | card_number: “4539146503757117” card_holder: “DIANA GIMSON” card_exp_month: “02” card_exp_year: “2029” card_cvv: “661” card_bin: PHILIPPINES | error: {code: 2.08, message: “Invalid card number”} |
16 | card_number: “5199914302370491” zip_code: 99801 | error: {code: 5.08, message: “Invalid transaction”} |
17 | card_number: “4945960509912296” zip_code: 99801 | error: {code: 2.09, message: “Invalid expiration date”} |
18 | card_number: “5261820900437819” zip_code: 99801 | error: {code: 3.06, message: “Debit card not supported.”} |
19 | card_number: “4857027008185133” card_holder: “DRAEN BARROS ” card_exp_month: “09” card_exp_year: “2029" card_cvv: “478” card_bin: GERMANY | error: {code: 2.10, message: “Invalid 3DS flow on the merchant side.”} |
20 | card_number: “5539974195624197” card_holder: “JAXON PECIGUS ” card_exp_month: “07” card_exp_year: “2029" card_cvv: “472” card_bin: SPAUN | error: {code: 5.01, message: “3D secure verification failed.”} |
21 | card_number: “5134431550984251” zip_code: 99801 | error: {code: 3.07, message: “Card token not found.”} for recurrent transactions only |
22 | card_number: “4983102885450335 ” card_holder: “ERROR AGAIN ” card_exp_month: “01” card_exp_year: “2029" card_cvv: “111” card_bin: FRANCE | error: {code: 4.02, message: “Stolen card.”} |
23 | card_number: “4222192107639022 ” card_holder: “Aleksandr Nabalnii ” card_exp_month: “08” card_exp_year: “2029" card_cvv: “759” card_bin: GERMANY | error: {code: 4.04, message: "Lost card.”} |
24 | card_number: “4907428874384745 ” card_holder: “Boris Mentsov ” card_exp_month: “10” card_exp_year: “2029" card_cvv: “123” card_bin: GERMANY | error: {code: 3.08, message: “Do not honor.”} |