Integration Checklist

You need to ensure that your Craftgate integration is progressing smoothly, is complete, and is ready for use in the live environment.
To assist you, we have prepared a checklist. You can go through this list and perform the necessary checks.

Development and Go-Live Phase

Topic	Our Recommendation
Will you integrate via API?	If you plan to integrate via API, we recommend using our Open Source Libraries written in different programming languages for seamless communication with Craftgate.
Have you processed payments using our test cards in the Sandbox environment while testing the flows?	During the final stage of development, you can test all your payment flows, including payments, cancellations, and refunds, in Craftgate's Sandbox environment. You can observe both successful and failed scenarios.
Can you properly display error messages?	You should capture errors with a code below 10000 and return a standard error message to the user. You can also display the error messages provided by Craftgate.
Will you accept payments with stored cards?	If you want to allow customers to save their cards and make payments using stored cards, your POS terminals must support CVV-less payments.
Does your POS have refund authorization for both its own bank cards and cards from other banks?	In some banks, the refund process requires separate authorization. Check with your bank regarding refund authorization and maximum limits.
Will you accept payments with corporate cards?	Many banks impose installment restrictions on corporate cards. These restrictions are pre-configured in Craftgate, but if you are managing installments yourself, you should use our BIN service to check for corporate cards and apply installment restrictions accordingly.
Will you accept payments from foreign cards?	If you plan to accept foreign cards, you must enable foreign card payments on your POS. If you do not wish to accept them, you can disable foreign payments from your POS settings in the Craftgate panel.
Will you accept payments with American Express cards?	You should check the card institution using our BIN service. For AMEX cards, the CVV length is 4 digits. Ensure you implement the correct CVV length validation.
Will you offer installment payments, or will all transactions be single payments?	If you are offering installment payments, verify that installment commissions are correctly and completely configured in your POS terminals.
Will you accept Non-3DS payments, or will all transactions be 3DS only?	You can set your desired POS terminal as "3DS Only" in the POS settings in the Craftgate panel.
Does your POS use a 3D Secure payment model other than “3D Model”?	We do not recommend the 3DPay model since the payment is finalized at the bank as soon as the user authenticates. However, Craftgate's "detect unresponsive payments" feature helps prevent issues where "a payment is processed, but an order is not created" due to the 3DSPay flow.
Do you need to send specific information (e.g., order number, policy number) to the bank with each payment?	You can send this information using the external ID. However, if you need this information specifically in the "order ID" field, confirm this with your finance team and verify payments in the payment screens before proceeding.
Do you want to manually determine which POS will process the payments?	If you allow Craftgate to handle POS routing, our auto-pilot routing algorithms will send payments to the most suitable POS. However, if you want to manage it yourself, you can specify a POS alias in the payment request to direct the transaction to a specific POS.
Do you want to add an interest charge for installment payments?	If you are integrating via API, you should use the price and paidPrice fields to apply interest charges. If you are using Craftgate's shared payment form, you should configure the necessary settings in the Craftgate panel.
Have you performed hash validation for 3DS payments?	For security reasons, you must perform hash validation. See our Security Recommendations page for more details.
Have you performed hash validation in your webhook integration?	To ensure that the webhook request originates from Craftgate, you must perform hash validation. See our Security Recommendations page for more details.
Have you enabled the Autopilot feature for your POS terminals?	To prevent payment disruptions due to possible system issues at banks, you should enable the auto-pilot feature.
Has your POS been tested by the Craftgate team?	Before going live, we require your POS terminals to be thoroughly tested by the Craftgate team.
Have you connected your system to the Craftgate live environment and tested payments using real cards?	Once your integration is complete, you must perform test payments using real cards before making it available to customers. You should carefully analyze error groups and messages returned by banks.

Post-Go-Live Checks

Topic	Our Recommendation
Have you checked potential validation errors from your payments in the Craftgate merchant panel?	You should track validation errors and analyze any issues.
Have you set up Proactive Monitoring rules to track payment success rates?	With proactive monitoring, you can be alerted to sudden drops in your success rate and take action.
Have you configured fraud prevention rules for suspicious transaction management?	You can define fraud prevention rules in the fraud management interface to protect against potential attacks.

For any questions or support needs, please contact the Craftgate team.