Subscriptions without associated plan - Configuration - Mercado Pago Developers

Subscription with no associated plan

Subscriptions with no associated plan are when different subscriptions have different characteristics because they are specific to each payer. A single-month subscription with a unique discount, for instance.

This subscription model can be

Subscriptions with authorized payment

Subscriptions with authorized payment allow an installment to be generated and billed based on a defined recurrence, causing the subscription engine to automatically schedule and create payments based on the payment method defined at the time of the subscription creation.

To offer subscriptions without an associated plan and with authorized payment, send a POST with the necessary attributes to the /preapproval endpoint and pay attention to the status parameter, which must be filled in with the value authorized.

After completing the fields, execute the request.

Important
We make a payment with a minimum amount to prove the card's validity. If it is successful, we will proceed with returning that payment. The value may differ according to each country.

Collection reattempt logic

By automating the recurrence of your collections, authorized payments that will have a debit date configured based on the periodicity that was defined in the subscription are created. The first installment is charged until the period of approximately one hour to subscribe.

Payment statuses

At the time the installment is collected, three alternatives may arise, based on the outcome of the payment:

  • Payment is successfully made so, the installment will remain as processed and will not be reattempted.

  • Payment is being processed so the installment will be pending in a waiting for gateway status until the payment is resolved.

  • Payment is declined so the installment will always remain in recycling status and when the installment is not expired or has not reached the maximum number of reattempts. Otherwise, it will be processed with the processed status.

Declined payments

When an installment remains in recycling status, it enters a reattempt scheme with a maximum of 4 possibilities, when the installment is collected again. The result can be any of the three points mentioned above.

If the payment is declined, it is updated to a new collection date by adding 1 of the 4 possibilities within ten days as a reattempt time window to the last available date.

By default the reattempt is within a 10 day window. In case the installment has an expiration date, the time window is adjusted to that date and maintains the logic of 4 reattempts.

Payments in process

If an installment is in waiting for gateway status and, when the payment is resolved, it appears as declined, and the expiration date is met, the installment will automatically appear as processed with the processed status. Otherwise, it will enter the reattempt scheme.

In the case that the installment cannot be collected on the fourth reattempt, it will automatically remain in processed status, associated with a declined payment.

After 3 installments with rejected payments, the subscription is automatically canceled and the seller account will be notified of the cancellation of the subscription by e-mail.

Note
The result of one installment does not affect the generation and processing of the remaining installments for the same subscription.

Subscriptions with pending payment

Subscriptions with pending payments are a model in which the payment method is not defined when the subscription is created. According to this model, payments automatically go into pending status and depend on the users to complete it.

In this case, there are two options: The first one is to update the subscription by defining a payment method through the /preapproval/{id} endpoint. The second one is to share a payment link with the buyer so they can complete the purchase with the payment method of their choice.

To offer subscriptions without an associated plan and with pending payments, send a POST with the necessary attributes to the /preapproval endpoint and then pay attention to the status parameter, which must be filled in with the pending value.

After completing the fields, execute the request.