/* Import Instrument Sans from Google Fonts */
@import url('https://fonts.googleapis.com/css2?family=Instrument+Sans:ital,wght@0,400;0,500;0,600;0,700;1,400;1,500;1,600;1,700&display=swap');

/* Apply Instrument Sans globally */
:root {
  --font-family-base: 'Instrument Sans', -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Oxygen, Ubuntu, Cantarell, sans-serif;
}

/* Override default font families */
body,
html {
  font-family: var(--font-family-base) !important;
  letter-spacing: 0.02em;
}

/* Headings */
h1, h2, h3, h4, h5, h6 {
  font-family: var(--font-family-base) !important;
}

/* Navigation and UI elements */
.mintlify-navigation,
.mintlify-sidebar,
.mintlify-navbar,
nav {
  font-family: var(--font-family-base) !important;
}

/* Content areas */
.mintlify-content,
.markdown,
article,
p,
span,
div {
  font-family: var(--font-family-base) !important;
}

/* Paragraphs and text content */
p {
  letter-spacing: 0.01em;
  line-height: 1.6;
}

/* Code blocks - keep monospace for readability */
code,
pre,
.code-block,
.highlight {
  font-family: 'JetBrains Mono', 'Fira Code', Monaco, Consolas, 'Liberation Mono', 'Courier New', monospace !important;
}

/* Buttons and interactive elements */
button,
.button,
.btn,
input,
select,
textarea {
  font-family: var(--font-family-base) !important;
}

/* API documentation specific elements */
.api-method,
.api-endpoint,
.parameter-name {
  font-family: var(--font-family-base) !important;
}

/* Search box */
.search-input,
.search-box input {
  font-family: var(--font-family-base) !important;
}

/* Tables */
table,
th,
td {
  font-family: var(--font-family-base) !important;
}

/* Ensure proper font weights are available */
.font-light { font-weight: 400; }
.font-medium { font-weight: 500; }
.font-semibold { font-weight: 600; }
.font-bold { font-weight: 700; }

{
  scrollbar-width: none !important;
  -ms-overflow-style: none !important;
}

*::-webkit-scrollbar {
  display: none !important;
}

[class*="language-"],
.highlight,
pre {
  scrollbar-width: auto !important;
  -ms-overflow-style: auto !important;
}

[class*="language-"]::-webkit-scrollbar,
.highlight::-webkit-scrollbar,
pre::-webkit-scrollbar {
  display: block !important;
}


How to Generate Your API Key

Configuring Authorization in API Tools (Postman)

Managing API Keys

Get API Keys

Your unified BNPL orchestrator for smarter payment processing

GreenBanana

Match. Connect. Convert. Your unified BNPL orchestrator for smarter payment processing

Welcome to GreenBanana

About Us

BNPL Flow

Environments

Quickstart

Account Setup

Setup Connector

First payment

Dashboard Overview

Webhook

Error Codes

Rate Limits

Go-live Checklist

Overview

**Use this API to initiate a payment.**

When you create a payment, it is stored with GreenBanana. At this stage, the payment intent is generated but requires confirmation from either the user or merchant to proceed.

Once confirmed (by including confirm=true and payment_method), the request is sent to the selected BNPL provider to verify if the customer is eligible for credit to proceed with the Buy Now, Pay Later (BNPL) provider.

The following request body example demonstrates how to create a payment with GreenBanana, which can be processed through any BNPL provider.

**Note:** The `metadata` field is used to carry additional information required by the BNPL provider. We have compiled all necessary metadata fields to ensure compatibility with any BNPL provider.

Payments - Create

**Use this API to confirm the payment and forward it to the BNPL provider.**

Alternatively, you can confirm the payment directly in the *Payments/Create* API by setting `confirm=true`. After confirmation, the payment may result in one of the following outcomes:

Once payments confirm is successfully completed, we will have payment status as `requires_capture` or `succeeded` indicating the amount for customer is authorized by the BNPL provider

1. **Fail** with a `failed` status.
2. **Transition** to a `requires_customer_action` status, along with a `next_action` block.
3. **Succeed**, with either:
- `succeeded` (for automatic capture), or
- `requires_capture` (for manual capture).

`BNPL providers typically use methods like `manual_capture` or `manual_multiple_capture` for capturing payments, as specified in the Payments Create request.

You can configure routing rules to process specific payments through specific connectors. If you would like to route a specific payment with specific connector you can also pass
"connector": ["connector_name"] to process the payment.


Payments - Confirm

To capture the funds for an uncaptured payment

Payments - Capture

A Payment could can be cancelled when it is in one of these statuses: `requires_payment_method`, `requires_capture`, `requires_confirmation`, `requires_customer_action`.

Payments - Cancel

To update the properties of a *PaymentIntent* object. This may include attaching a payment method, or attaching customer object or metadata fields after the Payment is created

Payments - Update

Retrieves a Payment. This API can also be used to get the status of a previously initiated payment or next action for an ongoing payment

Payments - Retrieve

Payments - List

Authorized amount for a payment can be incremented if it is in status: requires_capture

Payments - Incremental Authorization

Creates a session object or a session token for wallets like Apple Pay, Google Pay, etc. These tokens are used by Green Banana's SDK to initiate these wallets' SDK.

Payments - Session token

To retrieve the properties of a Payment Link. This may be used to get the status of a previously initiated payment or next action for an ongoing payment

Payments Link - Retrieve

External 3DS Authentication is performed and returns the AuthenticationResponse

Payments - External 3DS Authentication

Payments - Complete Authorize

Creates a refund against an already processed payment. In case of some processors, you can even opt to refund only a partial amount multiple times until the original charge amount has been refunded

Refunds - Create

Updates the properties of a Refund object. This API can be used to attach a reason for the refund or metadata fields

Refunds - Update

Retrieves a Refund. This may be used to get the status of a previously initiated refund

Refunds - Retrieve

Lists all the refunds associated with the merchant, or for a specific payment if payment_id is provided

Key	When to Use
Secret Key (api-key)	Used to authenticate API requests from your merchant server. Don’t expose this key on a website or embed it in a mobile application.
Publishable Key	Used to authenticate API requests from your app’s client. Can be publicly-accessible in your web or mobile app’s client-side code.

Introduction

First Steps

Essentials

Get API Keys

How to Generate Your API Key

Configuring Authorization in API Tools (Postman)

Managing API Keys

Introduction

First Steps

Essentials

​

​How to Generate Your API Key

​Configuring Authorization in API Tools (Postman)

​Managing API Keys

How to Generate Your API Key

Configuring Authorization in API Tools (Postman)

Managing API Keys