The table below describes the different PayIn methods available with the MANGOPAY API, and which capabilities are available for each. Note that for certain card payments, there may be an extra step for 3D-Secure to be completed - you can read more about the triggers for this step here.

	PayIn Web	PayIn Direct	3DSecure	Refund	Currency	Payment Type
CB/Visa/Mastercard	Yes	Yes	Yes	Yes	All	Card
Maestro	Yes	Yes	Always 3DS	Yes	EUR	Card
Diners	Yes	Yes	No	Yes	EUR	Card
Przelewy24	Yes	No	No	Yes	PLN	Card
iDeal	Yes	No	No	Yes	EUR	Card
Bancontact/Mister Cash	Yes	Yes	Always 3DS	Yes	EUR	Card
PayLib	Yes	No	No	Yes	EUR	Card
Sofort	Yes	No	No	Yes	EUR	Direct Debit
Giropay	Yes	No	No	Yes	EUR	Direct Debit
Direct Debit	No	Yes	No	Yes	EUR/GBP	Direct Debit
Bankwire	No	Yes	No	No	All	Bankwire

A Pay-in by card and via web interface is a request to process a payment to a wallet for a dedicated user.

You need to do your tests in sandbox mode only with the testing cards.

Note that you can fully customise the design of your payment page - more info here.

The Card Direct PayIn Object lets you pay with a registered Card (token). Here are the steps to follow:

1. Complete the CardRegistration steps (From 1. to 9. in the diagram here)
2. Create a Direct PayIn object with the CardId received through the CardRegistration (10. in the diagram here)
3. You need to do your tests in sandbox mode only with the testing cards

Remember that you must include the "Powered by MANGOPAY" banner on your payment page - you can download it here

Payment Flow

Here is the CardRegistration flow (tokenization) then the Direct PayIn:

Pre-authorized a card before the Pay-In ensures the solvency of a registered card for 7 days.

The overall process is as follows:

• Register a card (CardRegistration)
• Create a PreAuthorization with the CardId. This allow you to charge an amount on a card.
• Charge the card through the PreAuthorized PayIn object (Payins/preauthorized/direct).

How PreAuthorization + validation (Pay-In) works?

• Once the PreAuthorization object gets Status = "SUCCEEDED" and PaymentStatus = "WAITING" you can charge the card through a PreAuthorized PayIn.
• The PayIn amount has to be less than or equal to the amount authorized.
• If a PreAuthorized PayIn fails, you can re-use the same Preauthorization to create a new PayIn while the PreAuthorization has not expired.

Remember that you must include the "Powered by MANGOPAY" banner on your payment page - you can download it here

Note that for Maestro card, you must capture the full amount of the PreAuthorization. You can't capture less.

A bank wire PayIn is a request to process a payment by bank wire. The workflow is the following:

• Call the /payins/bankwire/direct object. You’ll receive MANGOPAY bank account details and a reference.
• Display this information to your user
• The user has to proceed a Bank wire to the display bank account with the reference
• Once MANGOPAY receive the payment the e-money is created and the targeted e-wallet is credited.

A bankwire by "external instruction" is a slightly particular payin whereby it is created when we receive funds for a banking alias - this means there is no way of creating a payin of this kind via the API (in sandbox, please contact our support team for them to create some examples for you).

A PayIn by direct debit and via web is a request to process a payment to a wallet for a dedicated user.

• There is no possibility of recurring payment for the moment with SOFORT and GIROPAY.
• Please use the testing accounts described here testing rules. If you use your own account even in sandbox you will actually be debited!

A PayIn by direct debit with a mandate is a request to process a payment to a wallet for a dedicated user.

• To use this payin method, you must have already created and submitted a Mandate (in a similar way to doing a direct card payin)
• Late failures: note that due to the nature of this payment method, it is possible to have a "late failure" which is when the payment Status is already "SUCCEEDED" but later on, the bank pulls back the funds and to reflect that in the API, we will create a Dispute (and hence Repudiation) with the DisputeReasonType being "LATE_FAILURE" which gives more information regarding the reason. In BACS (UK) the majority of late failures happen within 2/3 days. In SEPA, all late failures are within 5 days.
• Refunds are available for these PayIns, but you should know that a user can also dispute a payment and his bank will automatically refund it (for SEPA payments, this can be up to 8 weeks after the payment was made; for BACS, there is no time limit for a dispute) – there is no way to contest these decisions and we will create a normal Dispute
• Payment for direct debit payins is not taken instantly, and there will therefore be a delay before the transaction has theStatus of "SUCCEEDED". In the majority of cases, the timing is as follows:

• As with the submission of a mandate, we will notify the user of all upcoming payments on your behalf (the design of this email can be lightly customised – see here)
• For testing payments, you should use a specific value for the FirstName of the user owning the mandate
  1. "Successful" will result in a successful payment
  2. "Penniless" will result in a failed payment due to lack of funds
  3. "Fickle" will result in a successfull payment, which is disputed by the user and hence a dispute is created
• Mandate and direct debit payins are only available for certain business types, and is not activated by default – please contact your sales manager for more info
• For BACS payments, you should know that the banks Natwest, RBS, HSBC, Metro and Nationwide will not show your client name with payments, and only "MANGOPAY" will be shown

It is possible to add funds to your Credit/Repudiation Wallets via a PayIn Bankwire in order to settle the funds after a dispute. This endpoint can be used only for this purpose. For more information check The Settement Transfer object on the doc

The Pay-in web extended view is a view to get more details about the card used to process a payin web.