Se actualizó este documento.
La traducción en español no está disponible todavía.
Actualización del documento en inglés: 15 de abr.
Actualización del documento en español: 1 mar. 2023

Overview of Meta Pay Integration

You can integrate Meta Pay into your online store and customers can use the Meta Pay button to check out. Meta Pay is a seamless and secure way for customers to make payments online. For more information, see Meta Pay.

The Meta Pay button looks like the following:



Merchants use Meta Pay to create and submit payment transactions, and payment processors authorize or decline payments and record payment activity.

Payment providers must notify Meta of payment transaction activity so that it appears in the Facebook Pay Activity page of the customer's Facebook account.

Prerequisites

Before you can integrate Meta Pay into your online store or process payments for Meta Pay, you must satisfy the following prerequisites:

  • You must process raw card data by using the Payment Card Industry Data Security Standard (PCI-DSS). For details, see the PCI Document Library.

  • You must not rely on a third-party to host the checkout experience for your website. You must be able to use the JavaScript SDK for Meta Pay to create the Meta Pay button and display it on your website in the checkout user interface.

  • You must notify Meta of payment transaction activity by integrating with the Meta Pay API and by using webhooks. To learn how to use Meta's Graph API, see Overview of the Graph API.

If you satisfy the prerequisites, email Meta-Pay-Partnerships@meta.com to request access.

Onboarding

You may be onboarded as a checkout partner, payment partner, or both. Meta Pay will work with you to determine your designation as this will determine the required onboarding steps. A successful integration requires both a checkout partner and a payment partner. After you are approved to integrate with Meta Pay, you'll do the following steps to onboard with Meta Pay:

Checkout Partner Onboarding

  • Integrate Meta Pay JavaScript SDK in your checkout page
  • Pass the Payment Container returned from the JavaScript SDK to your Payment Partner for processing
  • Ask your Payment Partner to onboard you as a merchant on Meta Pay platform. They will execute a call to Merchant onboarding API on your behalf.

Payment Partner Onboarding

Workflow

A simplified version of the Meta Pay workflow looks like the following:

  1. Payment Partner registers merchant with Meta Pay
  2. The merchant site renders the Meta Pay button in the checkout user interface. (JavaScript SDK)
  3. The customer clicks the Meta Pay button.
  4. The merchant site opens the Meta Pay payment sheet and the customer enters data. (JavaScript SDK)
  5. The customer clicks Pay.
  6. The merchant site submits the payment details to the payment partner. (JavaScript SDK)
  7. The payment partner authorizes or declines the payment.
  8. The payment partner notifies Meta of all activity related to the transaction, including captures, authorizations, payments, disputes, and refunds. (Meta API)

The following illustration contains an overview of the workflow:

Test Environment

The test environment provided for testing your application is a shared resource that operates on a "best efforts" basis. This means that while we strive to provide a stable and reliable testing experience, there may be times when the test environment is unavailable or experiences issues that can impact your testing process.

Please note that there is no Service Level Agreement (SLA) associated with the test environment. This is because the test environment is intended to be used for experimental purposes and may not always behave as expected. As such, we recommend using the test environment primarily for testing and experimentation purposes, rather than relying on it for critical business operations.

If you encounter any issues with the test environment, please feel free to reach out to our support team for assistance. However, please be aware that we may not be able to address all issues or provide extensive support for test environment-related problems due to the experimental nature of this environment.