Instant Withdrawal - Interchecks
About Interchecks
Interchecks are an instant card withdrawal method. Interchecks is tailored for iGaming purposes and empowers VISA Direct consumers to withdraw their funds rapidly, with the amount becoming available for use within seconds.
Interchecks at a glance
Payment type | Card
|
---|---|
Consumer markets | United States (US) |
Processing currency | USD |
Single payments | No |
Merchant-initiated payments | No |
Withdrawals | Linked
|
Disputes | NA |
Guarantee | NO |
Refunds | NO |
Reporting | You can review your transactions in the Paysafe business portal and detailed reports on the Interchecks portal. |
Funding | For withdrawals, you maintain a liquidity balance with Interchecks, which you need to fund through wire transfer. |
Languages supported | EN |
Prerequisites
To use Interchecks on a gateway, you need:
- Standard Paysafe credentials.
- A contract with Paysafe and technical integration with Interchecks. You need to provide the following details to Paysafe:
- For withdrawals: Client ID, Client Secret, and Payer ID.
An assigned solution engineer/ support manager can guide you through these steps.
Certification
Paysafe's certification is sufficient. It is optional to obtain a separate certification with Interchecks if you have already been certified by Paysafe.
Supported use cases 
You can make the following types of transactions:
- Use case 1: Withdrawals with saved cards.
- Use case 2: Withdrawals with Apple Pay cards.
Use Case 1: Withdrawals with Saved Cards
When customers withdraw using cards saved in their Apple Pay wallet, a tokenized version of the card is used through the Apple Pay SDK.
To do a payout/withdrawal using Interchecks:
- Create a consumer and save the card.
- After saving the card to the consumer, call the withdrawal endpoint for all transactions:
- By calling the Standalone Credit API, use the permanent paymentHandleToken and Interchecks specific account ID to complete the withdrawal.
- POST: paymenthub/v1/standalonecredits
- Upon completion of the transaction, you will receive a gateway.id that can be used for reconciliation purposes.
Note: For code examples and detailed explanations of the parameters, see Payments API Reference.
Use case 2: Withdrawals with Apple Pay cards
Apple Pay is a pass-through wallet that facilitates contactless payments by securely transmitting consumers' credit or debit card information to merchants. It acts as an intermediary, encrypting and tokenizing sensitive data to protect consumers' financial details. Integration with the Apple Pay SDK enables a seamless payment experience within apps or websites. To allow withdrawals using cards saved in the Apple Pay wallet of consumers involves using Apple Pay SDK, which gives a tokenized version of the card, and the remaining process remains the same.
- Apple Pay saved cards can only be used for withdrawals, not payments. Therefore, you should only display Apple Pay cards as saved cards during the payouts/ withdrawals flow, not the payments flow.
- Only VISA Debit Cards are allowed for withdrawals using Apple Pay saved cards.
To do a payout/withdrawal using Interchecks:
- Get the tokenized card information using the SDK; the SDK response has to be passed in Payment Handle API. For more details, see Apple Pay.
- Complete the payment.
- Create the consumer and save the card.
- Once the card is saved to the customer, you can directly call the withdrawal endpoint for all transactions:
- Use the permanent paymentHandleToken and Interchecks specific account ID to complete the withdrawal using the Standalone Credit API.
- POST: paymenthub/v1/standalonecredits
- After completing the transaction, you will receive the gateway.id which can be used for reconciliation purposes.
To test Apple Pay, please use the Visa Debit card numbers provided on Apple Pay's Sandbox Testing page.
Appendix 
- Use the following BIN number.
- MC VISA and US DEBIT BIN: 514377 411774.
- Sample Cards
VISA | MasterCard |
---|---|
4117743221353359 4117744492503326 4117749879655490 4117749445933454 4117745498114513 4117749225034648 4117747516230610 4117749451647261 4117747282051521 4117747063157471 | 5143775365194442 5143773383937124 5143778046774970 5143778795941416 5143779352388967 5143771643717237 5143779341119127 5143773317766706 5143779504024551 5143773958176835 |
Simulation Cases
Simulation Amount in minor Unit (901=9.01 USD) | HTTP Error Code | API Response |
---|---|---|
901 | 503 | { "error": { "code": "1007", "message": "Gateway Error", "details": [ "Error communicating with downstream provider.", "Interchecks service is unavailable" ] }, "id": "64074eef-02c7-4f5d-b93d-90dd5cd206c8", "liveMode": false } |
902 | 402 | { "error": { "code": "3037", "message": "Your request has been declined because it is invalid.", "details": [ "ERR_OCT_DECLINE", "12:Invalid transaction" ] }, "id": "00321a88-8127-45ed-8b80-bd6bd61cbad5", "liveMode": false } |
903 | 502 | { "error": { "code": "1001", "message": "External Gateway Error.", "details": [ "ERR_TRANSACTION_FAILURE", "Error depositing funds" ] }, "id": "0593f4e8-c08a-431e-8ffd-8725cb0e6759", "liveMode": false } |
904 | 402 | { "error": { "code": "5021", "message": "Your transaction request has been declined.", "details": [ "ERR_INSUFFICIENT_FUNDS", "Insufficient funds" ] }, "id": "a5d03253-05ee-4f17-b284-69347638cfac", "liveMode": false } |
905 | 402 | { "error": { "code": "3027", "message": "The external processing gateway has reported a limit has been exceeded.", "details": [ "ERR_VELOCITY_LIMIT", "Transaction failed due to velocity controls" ] }, "id": "3c15bb2f-94df-408c-83ee-3a216d57df24", "liveMode": false } |